It is a real-time system, so calculation must happen when a row is added. I assure you, real-time collaborative formula calculation mandates this level of complexity.
Using batch operations with the cells feed would resolve this latency issue, because it would be a single operation to calculate, not many small ones. -Vic On Mon, Mar 19, 2012 at 4:13 AM, MZ <[email protected]> wrote: > We solved the problem. We had other sheets in the spreadsheet that did > calculations based on the data sheet. So as a very smart system it > seems that Google executes the whole spreadsheet meaning every sheet, > every time you add a row to a sheet. > > I must say that this is the dumbest system I have encountered for a > long, long time... > > On Mar 13, 10:43 am, MZ <[email protected]> wrote: > > Hey Vic. > > > > Yes, we are using list feed. Currently there's about 1000 rows but I have > > tried with empty sheet and it takes as long. > > > > There's 0 functions in that particular sheet but there's other sheets in > > that spreadsheet that do lookups and calculations based on the imported > > data. > > > > > > > > > > > > > > > > On Monday, March 12, 2012 4:57:09 PM UTC+2, Vic Fryzel wrote: > > > > > Please confirm that you're using the lists feed? > > > > > Can you tell me about the size of the sheet you're working with? How > many > > > rows/cols does it have? How many functions? > > > > > Thanks, > > > -Vic > > > > > On Mon, Mar 12, 2012 at 4:04 AM, MZ <[email protected]> > wrote: > > > > >> I have a script that imports rows to a specific spreadsheets. It > worked > > >> great last week but now I'm getting extremely slow replies from > > >>https://spreadsheets.google.com. I'm running the script right now and > > >> I'm getting average of 20 SECONDS of waiting per inserted row. As you > can > > >> imagine, when I have over 1000 rows to import, 20 seconds per row is > > >> unacceptable. > > > > >> I have tried different servers and debugged the code and the problem > > >> really seems to be at Google's end. Anybody else experiencing this? > What > > >> could cause this? >
