Closed Bug 667122 Opened 14 years ago Closed 14 years ago

Retrieving quota information takes a really long time

Categories

(Cloud Services Graveyard :: Server: Sync, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: philikon, Unassigned)

Details

(Whiteboard: [qa-])

Retrieving quota information typically takes 10 seconds or longer for any of my actual and development accounts. At this point stuff like network latency etc. is almost negligible. I can see why computing quota could take a really long time (if you're SUM()ing over all database rows). But I remember Toby saying that it should be cached somehow. So if that's the case, it might be that it's not working as expected and we have a ghastly inefficiency somewhere. On the other hand, if we're ok with quota information taking so long to be returned, we might want to change the UX of the dialog a bit to indicate to the user that the server is totting up the numbers which might take a while (e.g. show a spinner or something)
Your total usage quota is cached and should be pretty fast. Your actual detail information is not cached, and when we discussed it, the word was that it wasn't something that would be called very often and, as a result, hasn't been optimized. 10s still sounds rather long for a query on a reasonable data set. If we think that we'll be displaying that a lot more often than originally planned, we should look into ways of improving performance there.
Whiteboard: [qa-]
I don't think there's anything to be done here unless we've changed out philosophy on how often to hit the details. I am doing some other work on quotas that may impact this in the future.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Product: Cloud Services → Cloud Services Graveyard
You need to log in before you can comment on or make changes to this bug.