@Justin Are you aware of any way to do that with Google Analytics. That is in fact what we use but I am unaware of any API that I could use to achieve that. It doesnt seem like this would let me integrate this all into my models easily.
@Norman Do you know of any good resources to do what you propose? I am getting familiar with Linux hosting (using Slicehost to mess around right now) and would like to know how to manipulate my server to do more powerful things. Cron is something I've been meaning to look into for a while, is it a difficult thing to grasp? @V How would I go about doing that? I'm not too familiar with how to manipulate threading. Is this a scalable solution? The software I'm working on is going to be getting about 3 million page views a month so it needs to be a robust solution. Is what you're proposing like what Sameer posted? @Sameer That looks very interesting Sameer, I will be looking into that shortly. That may be what I am looking for. Thanks for the link. @all I am looking for a solution that is very scalable and that can handle a lot of traffic (potentially up to 5 million page views a month, if not more). What is the best solution for this use case? As everyone has made clear, writing to the DB on every view is suicide, so are server logs and cron the way to go or can it be possible to use a middleware (like Sameer posted) without my server exploding into fireball? Ideally it would be something that I could associate with various models in my application that I can then use to have content sortable by most viewed, etc... Thank you all _so_ much for your feedback, I really appreciate your time! Cheers, Dana On May 27, 5:56 am, "Norman Harman" <[EMAIL PROTECTED]> wrote: > One user having to wait for the DB write it not the scalability issue. > > Every user having to wait cause your db is crushed under the load of > writing every time someone views a page is. > > > > V wrote: > > couldn't this be done by opening a new thread? that way the user > > doesn't have to wait while you write the DB, but you would just make > > it plain simple > > > V > > > On May 26, 5:17 am, "James Bennett" <[EMAIL PROTECTED]> wrote: > >> On Sun, May 25, 2008 at 9:08 PM, jonknee <[EMAIL PROTECTED]> wrote: > >>> Unless you cache the view. Just update it once an hour/day. > >> You still have to record the raw number of hits somewhere. Doing this > >> in the database, in real time, is often not possible because it does > >> lead to one write per page view. > > >> Periodically crunching server logs is often a better alternative. > > >> -- > >> "Bureaucrat Conrad, you are technically correct -- the best kind of > >> correct." > > -- > Norman J. Harman Jr. 512 912-5939 > Technology Solutions Group, Austin American-Statesman > ___________________________________________________________________________ > You've got fun! Check out Austin360.com for all the entertainment > info you need to live it up in the big city! --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
