I recently did some Sun Ray installations down here that implied SunFire T2000 servers.
The first setup with T2000 was with the 6 cores with 1 GHz UltraSPARC-T1 CPU. The setup was for using the T2000s only as connection servers (SRSS was configured to automatically opens Windows XP sessions on VMware servers with uttsc - nothing else was done on the T2000s). For this use, it was OK. But, before installing in CAM mode the servers, I did a basic SunRay connection test, and I opened a JDS desktop on one T2000... ...oh boy! This was very slow! Only CDE was acceptable, and even then, Mozilla/Firefox was a pain to start. So we had another installation request for another client, with 3 T2000s, but this time, the client wanted to use JDS sessions (approximately 400 concurrent sessions desserved by 3 x SunFire T2000). I was not that much excited with my previous experience. However, the T2000s used for this project was the ones with the 8 cores and 1.4 GHz UltraSPARC-T1 CPU, and 16gb of RAM each. This made a slight difference. JDS sessions, once hardened a bit, was very good. We did a test with over 50 JDS sessions opened on SunRays stations on a single T2000 server, with StarOffice apps, Firefox and file browsers opened, and we didn't notice even a small slowdown at all. >From my point of view, the second setup I did changed my mind about the use of T2000 in SunRay environments. However, I still consider these servers are really not interesting at all if you need floating point intensive applications, or if your applications use big-single-threads... This is a matter of fact, of course! Ben _______________________________________________ SunRay-Users mailing list [email protected] http://www.filibeto.org/mailman/listinfo/sunray-users
