Looking into server page stats with Wayne and Cory. Small bugs and tracking down sources. Wayne has released his new monitoring services on data 0. We were looking at page views and what not. The top page was the view cart page with over 22,000 views in just the first 5 days of launching the monitoring service. This is just on data 0, not even that busy of a server. Our servers get hammered, daily!

Cory had a number of questions for Wayne from emails and other projects that are circling around. We spent some time talking about memory issues on both the server-side and the client-side. This is kinda new, but we are starting to see more client-side memory issues. A normal page, the server handles all of the memory stuff. We can mostly control all of those pieces. On some of the new and fancy heavy JavaScript pages, it gets to be a big client-side load in order to keep all of that data quickly at hand (data loaded on the client-side in the browser). We will keep working with stuff, but may have to break things down into smaller and smaller pieces.

Some of our pages may need to be refactored. They are doing too much and/or requiring the browser to work too hard or store too much info. This may be something that we need to be aware of for our future fracture project. We have to balance both client-side and server-side memory management stuff. Just because we can use AJAX and JavaScript and cool data tables, that may not always be the answer. At some point, even those things fail. We need a good mix of both and make it as smooth as possible.