Hi Rodney, I did moved my ViewState into memory recently after I've moved this site http://www.goeatout.com.my/ to a dedicated server. However, I did not use much third party module with AJAX. I have another site using video module (that one you're using in your pokerdiy...I forgot the name) which cannot put the ViewState into memory...maybe AJAX issue... I believe your high processes is mainly due to that you have too many users logged on? I also noticed that Ventrian's PA wild card search has flaws on the wildcard search especially if you are using a single letter to search... I also trying hard to have my portal run faster...it's very slow in my country, not even counted heavy network latency due to poor international connectivity in my country. (about 6 secs to load a cached page for first time visitors and >10secs for those loaded from overseas...)

---

Thanks,
George

Where to eat? Visit GoEatOut for Food Promotion in Kuala Lumpur.

If you need an on demand lab for intense performance testing, let me know. We have a scalable setup using cloud hosting with 1 Web server, 1 stress agent, 1 SQL server, all controlled from a local Visual Studio that configures the stress agent and does code profiling + performance monitoring. Each server in the setup can scale from 1x 2.4 GHz CPU 1GB RAM to 8x 2.4 GHz 8GB RAM, and is paid on a hourly basis.

It's a great setup for load testing / profiling and capacity planning.

---

Move to a hosting provider that does NOT use excuses for hosting issues ... if you are running a standard dnn install - I would treat as dubious any claims about memory leaks being the cause for poor performance.

What I would more suggest - is that your HOST is limiting the amount of memory that is available to your application - to a point below which dnn is capable of operating effectively.   DNN requires around 250-300 meg or available memory to function.  Anything much below this and the application pool with start to recycle - and slow down everything.

Yes there are some things you can do to tinker around the edges - adjusting cache sizes - hacking the 52degrees mobile device code out of the core - moving to page based caching instead of memory - but in reality - you need to work with a host that understands the needs of a dnn system.

Memory is cheap - but some host are greedy - trying to overload shared hosts and squeeze the clients.  DNN is a complex and advance application system - it not a simple html page delivery system.  Treat it like that and it will work for you - treat it badly and well performance will be an issue.

Westa