Not sure if this is just me. But in performance analyser I can only see the total sync time for each table. Whereas before I could see than plus each virtual column.
1 Like
In my own applications I noticed that performance analyzer would only show virtual column time if it takes ‘longer’ than some internal threshold. Not sure what Appsheet deems to be the threshold, but that is the only time I would see specific analysis as it pertains to VCs.
I wouldn’t have thought that was an issue. I’m getting sync times in the 150 to 160 seconds range.
One other quirk is I’m not seeing any perfomance listings for sync I do via the App Definition
Yeah, at that kind of sync time I would expect the performance analyzer to show which VC(s) are causing the long sync times. That is exactly how I used it in the past when one of my apps took forever to load. Are you able to share a screenshot of the analyzer output?
1 Like
Yeah, I would call this as another bug, I see the same recently.
More oddly, on some cases (unable to reproduce), i see the performance log where all the operation is 0 sec, which is definitely not true.
1 Like
Escalated.
1 Like
Indeed . Not able to drill down to anywhere.
1 Like
Same. of course I find that I have users randomly spiking to the 20 second sync times because I found this but I can’t tell why
1 Like
Austin_Lambeth:
spiking to the 20 second sync times
I wish…
[Issues when sync times are very long (120sec+)](https://community.appsheet.com/t/issues-when-sync-times-are-very-long-120sec/43020) Questions
I’ve got a particually big app with sync times in excess of 2 mins. Because its so slow we are noticing a coupe of things that might not show up if it was quicker. On iPhones, the app does not use the internet when the App is minimised We have 30ish people who submit timesheets. They submit at least one per day, sometimes more. Inside each timesheet there wil be 1 to 10 items in a subtable. What we’ve seen is delays of 3-4 days from someone creating a timeentry to it showing up in google …
Any news on this @Steve after it was escalated?
2 Likes
I noticed this as well, thanks for reporting!
I’m told this may have been fixed in today’s release. Can anyone confirm?
Hi @Steve
This seems to be working ok now
1 Like