Hi Subodh,
10k records isn't that much. Nonetheless you should test your
application with high loads to assert if the database performance is an
issue.
If the test results show that the database performance may be a problem,
you should check if the tables you use are properly indexed and loo
10,000 people does not sound like too heavy a load. How often will they
check their schedules?
If you are looking up items by day and user, then indices on day and
(foreign key on) user should be enough to handle a much heavier load.
If you do find you need caching, using Django's built in cach
Rule #1: Measure first.
Don't add any complexity to fix any bottlenecks until you know for a
fact where they are. Once you know where one is, the solution will
probably be fairly obvious. Caching, denormalization, etc.
Come up with a way to stress-test your app and add measurements.
--
You rece
Hi,
I have implemented a django application that willl maintain schedule
for 100s of people that work for a company. People access this
schedule using desktop or mobile device to lookup their task list for
current day, this week etc.
Now the question is how do I scale this -- example when user jo
4 matches
Mail list logo