Earlier this week, co-workers and I did some performance testing with Memcached. We wanted to see how long it'd take to send different sizes of objects over the wire to Memcached on a remote server.
We setup a simple environment with 2 Mac Pros both running 2 x 2.8 Ghz Quad-Core Intel Xeon processors and 12GB of RAM. We used one machine as a Memcached server and one machine running an application with the addition of a new Servlet Filter. The Servlet Fitler read a size parameter and used it to set the size of the object being written and read from the Memcached server. We used JMeter to put load on the box. The following describes the load and the results.
Write Times
Write tests were performed with a single user executing 1000 sequential remove then writes.
| Size in Bytes |
Time (ms.) |
Min. Time (ms.) |
Max. Time (ms.) |
Total |
| 20000 |
1.31 |
0 |
7 |
1000 |
| 50000 |
1.834 |
1 |
8 |
1000 |
| 100000 |
2.87 |
2 |
9 |
1000 |
| 500000 |
12.641 |
9 |
283 |
1000 |
Read Times
Read tests were performed using 50 users with 1 sec. ramp times executing 100 reads each.
| Size in Bytes |
Time (ms.) |
Min. Time (ms.) |
Max. Time (ms.) |
Total
|
| 20000 |
4.8414 |
1 |
375 |
5000 |
| 50000 |
18.343 |
1 |
354 |
5000 |
| 100000 |
46.181 |
2 |
415 |
5000 |
| 500000 |
137.7328 |
6 |
953 |
5000 |
During our tests, Memcached was started using the following settings:
memcached -d -m 2048 -M -p 10171 -vv
If you've done similar performance testing with Memcached, we'd love to see your results.
Peter Mularien has a very well written post titled How Open Source is Spring?: An Analytical Investigation:
This post is to expand on some of the thoughts I posted on the SpringSource Blog in response to Rod Johnson's excellent description of the SpringSource business model and its commitment to development of open source software.
Now that SpringSource has shown an ability to crank out new product releases on a seemingly weekly basis, I wanted to reflect on where Spring is positioned in the Java open source community, and how open the Spring Core project is to work done by the public.
The hypothesis of my experiment occurred to me when I happened to be reviewing Spring JIRA assignments one day. I was curious whether, following the bug assignments, the majority of development on the "Spring Core" projects (including Spring MVC and what we would consider "classic Spring") is performed solely by SpringSource employees.
Peter's post is near and dear to me because I'm doing a What's coming in Spring 3.0 talk at the Colorado Software Summit in October. The only information I was able to find on Spring 3.0 is from random blog posts and Juergen's presentation. When I give talks about technologies, I prefer to dig in and try them before talking about it. With Spring 3.0's source code nowhere to be found, this is very difficult to do.
I really hope Spring 3.0 becomes available in early October. If it does, I hope to upgrade AppFuse, AppFuse Light and Spring Kickstart. If it doesn't, my talk will most likely be a regurgitation of what Juergen's slides have and that's just not right.
