November 25, 2008
The New Component Update - Help Requested
ok, so here’s what the new component WAS…
I created 8 Wordpress Multiuser domains and was going to let all The Wordpress Project customers in good standing create hubs on this system.
Once the infrastructure was created, I gave access to 20 customers and asked them to report back any issues they found.
Within minutes, the server crashed. I rebooted it and then 20 minutes later, it crashed again. This went on for several hours before I asked them to stop using the system.
Come to find out, the problem was the use of Caffeinated Content. My very beefy server just couldn’t handle 20+ instances of Caffeinated Content running at once.
Imagine if we had 100 users all using it at once?
So here’s where I need some help.
If you are an ultra techie, how can this issue be solved? The guys at SEO Hosting didn’t have a clue.
If I can’t get back any feedback on this, then I will have to put this bonus on hold until the server version of CC (which is less resource intensive) is released (and I have no idea when that will be).
Take care,
Keith
Comments on The New Component Update - Help Requested »
Keith,
I have my own servers for several of my own sites plus use hosted sites for others.
With the limited details that you’ve given the problem appears to be a combination of processor resources and RAM memory. When you say multiple copies of CC running that tells me that you are really loading up the RAM memory. Either more memory is desireable however, the real cure would be a milti-threaded Server Service based version of the application.
Unfortunitly, there’s no quick and cheap fix unless more RAM can be added. Not knowing the system configuration is really hampering a good suggestion.
Please feel free to contact me for more discussion.
Regards,
Gregg Sterner
Network Engineering Services - http://www.NetworkEngineeringServices.com
The Rookie Day Trader http://www.RookieDayTrader.com
Trader’s Gifts - http://www.TradersGifts.com
gregg@NESdomains.com
Carrollton, TX
Keith
I just had another thought.
There could be a memory leak in the CC application or it is not releasing memory when it closes. Check the cashing parameters for the application.
Again, more details about the server and application configurations would really help.
Regards,
Gregg Sterner
Network Engineering Services - http://www.NetworkEngineeringServices.com
The Rookie Day Trader - http://www.RookieDayTrader.com
Trader’s Gifts - http://www.TradersGifts.com
gregg@NESdomains.com
Carrollton, TX