![]() |
ChannelsRecent blog posts
Welcome to the PLoS BlogBlogrollWho Links to Us?Overall performance has been good since last week. We have to restart the stack three times a day due to the memory problem but these outages last less than 10 minutes. Since we have almost all caches shared with the new server, the sites come up very fast. Ingest of articles still slows down the sites but we have some ideas on how to make the ingest much faster. I've set up stress tests today with WebLOAD. It's a pretty useful tool with great reporting but it's not really an Open Source application. You can use WebLOAD up to 100 virtual clients but have to buy a license for anything beyond. But it's enough to stress test our multi-server stack if I set cache to a minimum. We've setup jProfiler to help diagnose the memory problems and hope to have some ideas where the memory leak is occurring soon. We're waiting for the Topaz developers to finish up code to serialize one last cache, move some data into the caches and a accelerate a couple of OTM queries. We should have a fix for search soon and may be able to put basic/advanced search back up on the journal websites soon if testing goes well. Reply |
|
Any opinions expressed in these blogs are the personal views of the contributors, and do not necessarily represent the views or policies of PLoS. Use of the PLoS blogs and the PLoS Web Sites is at all times subject to our Terms of Use.
|
Recent comments