The-WebOps-Club / fest-api

An API implementation for Saarang Shaastra like fests, including ERP and Mainsite and Mobile interface
12 stars 11 forks source link

Cache the user_list, dept_list, etc #86

Closed AbdealiLoKo closed 9 years ago

AbdealiLoKo commented 10 years ago

All these lists need a date field which the browser will tell the server and the server should give data or no data,

When giving data, just give the whole data (it's easier)

And save it into 4 localstorage variables.

very simple, and will make page load atleast 30% faster

AbdealiLoKo commented 10 years ago

Hey, Hey,

Please have discussoions here. Its very difficult for me to track so many things in every possible communications ever.

WHAT?
that's hardly 10kb total and what about all the background get_user_info AJAX calls. it's making about a thousand of them
but still according to chrome's timeline, the total load time is about 18.5s
In a given 3 s over 10 resources are loaded including the 3 json files.
so currently caching them shouldnt do much good except probably release a little load on the server?

The reason u got a fast page load was cuz you fif not clear your cache. You and I go to ERP about 20 times a day. So, chrome caches everything. Clear your cache and try. My stats : Total page load time ~60 sec Time due to get_infos ~20sec Page lists took ~10sec

When I load it the second time, I got the same stats. Because google still doesn't think erp is high priority (visited only twice) and will prefer caching google and fb static files. Localstorage is awesome, because it gives you control on what to cache.

When, It was never about the 10kb... IF we can do this cache, get_info will not be required. Because we can make the user_list.json and stuff bigger. So, basically they can hold email, phno and fbid by default. So, we'll be reducing atleast ~20sec in total for an average page load.

The only difference is that whenever someone changes their phno, or email, we have to regenerate the lists. Please have discussoions here. Its very difficult for me to track so many things in every possible communications ever.

WHAT?
that's hardly 10kb total and what about all the background get_user_info AJAX calls. it's making about a thousand of them
but still according to chrome's timeline, the total load time is about 18.5s
In a given 3 s over 10 resources are loaded including the 3 json files.
so currently caching them shouldnt do much good except probably release a little load on the server?

The reason u got a fast page load was cuz you fif not clear your cache. You and I go to ERP about 20 times a day. So, chrome caches everything. Clear your cache and try. My stats : Total page load time ~60 sec Time due to get_infos ~20sec Page lists took ~10sec

When I load it the second time, I got the same stats. Because google still doesn't think erp is high priority (visited only twice) and will prefer caching google and fb static files. Localstorage is awesome, because it gives you control on what to cache.

When, It was never about the 10kb... IF we can do this cache, get_info will not be required. Because we can make the user_list.json and stuff bigger. So, basically they can hold email, phno and fbid by default. So, we'll be reducing atleast ~20sec in total for an average page load.

The only difference is that whenever someone changes their phno, or email, we have to regenerate the lists.

Phoenix25 commented 10 years ago

oh okay.. my last point might have been wrongly phrased by 10 resources in 3s i did not mean how fast they loaded but that chrome loaded around 15 resources simultaneously and no the get_info request were not part of them and the given json files were also not the limiting factor. And also chrome loaded another batch of 15 resources after that . so i'm saying unless we take care of all of them it may not make much of a difference.

On Sat, May 31, 2014 at 11:12 AM, AbdealiJK notifications@github.com wrote:

Hey, Hey,

Please have discussoions here. Its very difficult for me to track so many things in every possible communications ever.

WHAT? that's hardly 10kb total and what about all the background get_user_info AJAX calls. it's making about a thousand of them but still according to chrome's timeline, the total load time is about 18.5s In a given 3 s over 10 resources are loaded including the 3 json files. so currently caching them shouldnt do much good except probably release a little load on the server?

The reason u got a fast page load was cuz you fif not clear your cache. You and I go to ERP about 20 times a day. So, chrome caches everything. Clear your cache and try. My stats : Total page load time ~60 sec Time due to get_infos ~20sec Page lists took ~10sec

When I load it the second time, I got the same stats. Because google still doesn't think erp is high priority (visited only twice) and will prefer caching google and fb static files. Localstorage is awesome, because it gives you control on what to cache.

When, It was never about the 10kb... IF we can do this cache, get_info will not be required. Because we can make the user_list.json and stuff bigger. So, basically they can hold email, phno and fbid by default. So, we'll be reducing atleast ~20sec in total for an average page load.

The only difference is that whenever someone changes their phno, or email, we have to regenerate the lists. Please have discussoions here. Its very difficult for me to track so many things in every possible communications ever.

WHAT? that's hardly 10kb total and what about all the background get_user_info AJAX calls. it's making about a thousand of them but still according to chrome's timeline, the total load time is about 18.5s In a given 3 s over 10 resources are loaded including the 3 json files. so currently caching them shouldnt do much good except probably release a little load on the server?

The reason u got a fast page load was cuz you fif not clear your cache. You and I go to ERP about 20 times a day. So, chrome caches everything. Clear your cache and try. My stats : Total page load time ~60 sec Time due to get_infos ~20sec Page lists took ~10sec

When I load it the second time, I got the same stats. Because google still doesn't think erp is high priority (visited only twice) and will prefer caching google and fb static files. Localstorage is awesome, because it gives you control on what to cache.

When, It was never about the 10kb... IF we can do this cache, get_info will not be required. Because we can make the user_list.json and stuff bigger. So, basically they can hold email, phno and fbid by default. So, we'll be reducing atleast ~20sec in total for an average page load.

The only difference is that whenever someone changes their phno, or email, we have to regenerate the lists.

— Reply to this email directly or view it on GitHub https://github.com/The-WebOps-Club/fest-api/issues/86#issuecomment-44718714 .

AbdealiLoKo commented 10 years ago

Well, cacheing everything is not possible ...

Let's start with this ? I think it's the most important thing ... As if someone sees an post an replies these lists,are needed. Sometimes it cups and doesn't download ...

Plus, with the current hundred users, you may not see it... But with 800 users, it will be a big impact On Sat, May 31, 2014 at 12:19 PM, Sai Praveen B notifications@github.com wrote:

oh okay.. my last point might have been wrongly phrased by 10 resources in 3s i did not mean how fast they loaded but that chrome loaded around 15 resources simultaneously and no the get_info request were not part of them and the given json files were also not the limiting factor. And also chrome loaded another batch of 15 resources after that . so i'm saying unless we take care of all of them it may not make much of a difference.

On Sat, May 31, 2014 at 11:12 AM, AbdealiJK notifications@github.com wrote:

Hey, Hey,

Please have discussoions here. Its very difficult for me to track so many things in every possible communications ever.

WHAT? that's hardly 10kb total and what about all the background get_user_info AJAX calls. it's making about a thousand of them but still according to chrome's timeline, the total load time is about 18.5s In a given 3 s over 10 resources are loaded including the 3 json files. so currently caching them shouldnt do much good except probably release a little load on the server?

The reason u got a fast page load was cuz you fif not clear your cache. You and I go to ERP about 20 times a day. So, chrome caches everything. Clear your cache and try. My stats : Total page load time ~60 sec Time due to get_infos ~20sec Page lists took ~10sec

When I load it the second time, I got the same stats. Because google still doesn't think erp is high priority (visited only twice) and will prefer caching google and fb static files. Localstorage is awesome, because it gives you control on what to cache.

When, It was never about the 10kb... IF we can do this cache, get_info will not be required. Because we can make the user_list.json and stuff bigger. So, basically they can hold email, phno and fbid by default. So, we'll be reducing atleast ~20sec in total for an average page load.

The only difference is that whenever someone changes their phno, or email, we have to regenerate the lists. Please have discussoions here. Its very difficult for me to track so many things in every possible communications ever.

WHAT? that's hardly 10kb total and what about all the background get_user_info AJAX calls. it's making about a thousand of them but still according to chrome's timeline, the total load time is about 18.5s In a given 3 s over 10 resources are loaded including the 3 json files. so currently caching them shouldnt do much good except probably release a little load on the server?

The reason u got a fast page load was cuz you fif not clear your cache. You and I go to ERP about 20 times a day. So, chrome caches everything. Clear your cache and try. My stats : Total page load time ~60 sec Time due to get_infos ~20sec Page lists took ~10sec

When I load it the second time, I got the same stats. Because google still doesn't think erp is high priority (visited only twice) and will prefer caching google and fb static files. Localstorage is awesome, because it gives you control on what to cache.

When, It was never about the 10kb... IF we can do this cache, get_info will not be required. Because we can make the user_list.json and stuff bigger. So, basically they can hold email, phno and fbid by default. So, we'll be reducing atleast ~20sec in total for an average page load.

The only difference is that whenever someone changes their phno, or email, we have to regenerate the lists.

Reply to this email directly or view it on GitHub < https://github.com/The-WebOps-Club/fest-api/issues/86#issuecomment-44718714>

.

Reply to this email directly or view it on GitHub https://github.com/The-WebOps-Club/fest-api/issues/86#issuecomment-44719587 .

AbdealiLoKo commented 9 years ago

@shahidhk : how much time does saarang erp take to load ? How many users are there on it ?

If it takes less time to load ... we can pack this.