The first cut of a Java EE implementation of Olio is now checked into the repository. The file docs/java_setup.html gives instructions on how to build and setup this implementation. The implementation uses JSP, servlets, JPA for persistence, yahoo and Jmaki widgets for AJAX etc. The web application is located in webapp/java/trunk and the load driver, database and file loaders etc. are in workload/java/trunk.
Check it out.
The first cut of a Java EE implementation of Olio is now checked into the repository. The file docs/java_setup.html gives instructions on how to build and setup this implementation. The implementation uses JSP, servlets, JPA for persistence, yahoo and Jmaki widgets for AJAX etc. The web application is located in webapp/java/trunk and the load driver, database and file loaders etc. are in workload/java/trunk.
Check it out.
If there's a site that exemplifies explosive growth, it has to be Twitter. It seems like everywhere you look, someone is Tweeting, or talking about Tweeting, or Tweeting about Tweeting. Keeping the site responsive under that type of increase is no easy job, but it's one that John Adams has to deal with every day, working in Twitter Operations. He'll be talking about that work at O'Reilly's Velocity Conference, in a session entitled Fixing Twitter: Improving the Performance and Scalability of the World's Most Popular Micro-blogging Site, and he spent some time with us to talk about what is involved in keeping the site alive.
James Turner: Can you start by describing the platforms and technologies that make Twitter run …
[Read more]As promised, here are more results running memcached on Sun's X2270 (Nehalem-based server). In my previous post, I mentioned that we got 350K ops/sec running a single instance of memcached at which point the throughput was hampered by the scalability issues of memcached. So we ran two instances of memcached on the same server, each using 15GB of memory and tested both 1.2.5 and 1.3.2 versions. Here are the results :
The maximum throughput was 470K ops/sec using 4 threads in memcached 1.3.2. Performance of 1.2.5 was just very slightly lower. At this throughput, the network capacity of the single 10gbe card was reached as the benchmark does a lot of small packet transfers. See my earlier post for a description of the server configuration and the benchmark. At the maximum …
[Read more]As promised, here are more results running memcached on Sun's X2270 (Nehalem-based server). In my previous post, I mentioned that we got 350K ops/sec running a single instance of memcached at which point the throughput was hampered by the scalability issues of memcached. So we ran two instances of memcached on the same server, each using 15GB of memory and tested both 1.2.5 and 1.3.2 versions. Here are the results :
The maximum throughput was 470K ops/sec using 4 threads in memcached 1.3.2. Performance of 1.2.5 was just very slightly lower. At this throughput, the network capacity of the single 10gbe card was reached as the benchmark does a lot of small packet transfers. See my earlier post for a description of the server configuration and the benchmark. At the …
[Read more]As promised, here are more results running memcached on Sun's X2270 (Nehalem-based server). In my previous post, I mentioned that we got 350K ops/sec running a single instance of memcached at which point the throughput was hampered by the scalability issues of memcached. So we ran two instances of memcached on the same server, each using 15GB of memory and tested both 1.2.5 and 1.3.2 versions. Here are the results :
The maximum throughput was 470K ops/sec using 4 threads in memcached 1.3.2. Performance of 1.2.5 was just very slightly lower. At this throughput, the network capacity of the single 10gbe card was reached as the benchmark does a lot of small packet transfers. See my earlier post for a description of the server configuration and the benchmark. At the …
[Read more]
Memcached is the de-facto distributed caching
server used to scale many web2.0 sites today. With the
requirement to support a very large number of users as sites
grow, memcached aids scalability by effectively cutting down on
MySQL traffic and improving response times.
Memcached is a very light-weight server but is known not to scale
beyond 4-6 threads. Some scalability improvements have gone into
the 1.3 release (still in beta). With the new Intel Nehalem based
systems improved hyper-threading providing twice as much
performance as current systems, we were curious to see how
memcached would perform on these systems. So we
ran some tests, the results of which are shown below :
memcached 1.3.2 does scale slightly better than 1.2.5 after 4
threads. However, both versions reach their …
Memcached is the de-facto distributed caching
server used to scale many web2.0 sites today. With the
requirement to support a very large number of users as sites
grow, memcached aids scalability by effectively cutting down on
MySQL traffic and improving response times.
Memcached is a very light-weight server but is known not to scale
beyond 4-6 threads. Some scalability improvements have gone into
the 1.3 release (still in beta). With the new Intel Nehalem based
systems improved hyper-threading providing twice as much
performance as current systems, we were curious to see how
memcached would perform on these systems. So we
ran some tests, the results of which are shown below :
memcached 1.3.2 does scale slightly better than 1.2.5 after 4
threads. However, both versions reach their …
Memcached is the de-facto distributed caching
server used to scale many web2.0 sites today. With the
requirement to support a very large number of users as sites
grow, memcached aids scalability by effectively cutting down on
MySQL traffic and improving response times.
Memcached is a very light-weight server but is known not to scale
beyond 4-6 threads. Some scalability improvements have gone into
the 1.3 release (still in beta). With the new Intel Nehalem based
systems improved hyper-threading providing twice as much
performance as current systems, we were curious to see how
memcached would perform on these systems. So we
ran some tests, the results of which are shown below :
memcached 1.3.2 does scale slightly better than 1.2.5 after 4
threads. However, both versions reach their …
I introduced Olio a little while ago as a
toolkit to help web developers and deployers as well as
performance/operations engineers. Olio
includes a web2.0 application as well as the necessary software
required to drive load against it. Today, we are showcasing the
first major deployment of Olio on Sun's newest Intel Nehalem
based systems - the SunFire
X2270 and the SunFire X4270. We tested 10,000 concurrent
users (with a database of 1 million users) using over 1TB of
storage in the unstructured object store.
The diagram below shows the configuration we tested.
The Olio/PHP web application was deployed on two X2270 systems.
Since these systems …