README: Clarify the test hardware.

README.md

@@ -45,7 +45,7 @@ The final image illustrates the situation with Spriths after removing the lock.
 Results
 -------
 
-So is something like this worth the effort? Well, probably; it'll depend on the specific usecase. The sample application context contained in this project loads in about 3.2 seconds using the standard _ClassPathXmlApplicationContext_, and in about 1.8 seconds using the custom _ThreadedClassPathXmlApplicationContext_ provided by this project. That's a savings of about 40%.
+So is something like this worth the effort? Well, probably; it'll depend on the specific usecase. The sample application context contained in this project loads in about 3.2 seconds on a 2.8 GHz Core 2 Duo (two CPU cores) using the standard _ClassPathXmlApplicationContext_, and in about 1.8 seconds using the custom _ThreadedClassPathXmlApplicationContext_ provided by this project. That's a savings of about 40%.
 
 However, using this in a couple of real-world applications showed gains more in the 15% to 20% range. Specifically, these applications were using Hibernate for JPA; JPA persistence context initialization was triggering retrieval of metadata from the database on startup. The network I/O generated by a single bean was consuming most of the startup time.