Domain: cassatt.com
Stories and comments across the archive that link to cassatt.com.
Comments · 9
-
Re:Costs haven't changed that dramatically
The otherr realy key metric is server utilization. It turns out the IT's dirty little secret is that the way they deploy applications (in static silos of servers that can't be shared between applications) requires that each app be dramatically over provisioned with hardware to handle various load changes. A typical data center is only using 10% of it's compute capacity at any given time. This has gotten dramatically worse as people moved from Mainframe->SMP->Cheap Pizza Boxes.
-Steve
http://www.cassatt.com/ -
XVM
-
XVM
-
Re:Are they x86 compatible?They're not x86 compatible. They're special purpose chips for Network Attached Processing devices for driving up utilization on Java applications. For another approach to driving up utilization on server-side Java applications you should check out Cassatt.
Cassatt was discussed on Slashdot a few weeks ago.
-Steve -
Re:Me Too!If you'd like to see an example of this kind of thing working today you should check out Cassatt
You can also check out this recent article in InformationWeek for an example of someone using it successfully.
-Steve
-
An Actual Case Study (link)If you'd like to see some details on what this does in a real customer setting you should check out this case-study on Cassatt at Pfizer.
Steve Wilson
Cassatt Corporation -
Here's a Translation
In english:
We use various technologies to allow us to efficiently and safely run more of your J2EE applications on fewer physical servers. By using fewer servers, but still maintaining your performance and availability characteristics, you can save a lot of money running your data center.
Does that help?
-Steve
Steve Wilson
Cassatt Corporation
http://www.cassatt.com/ -
Re:Sweet
Just an FYI for those of you who just joined us. Steve Wilson was the co-author of Java Platform Performance, along with Jeff Kesselman (the Java gaming dude, who still works at Sun). So he's pretty well versed in how Java technology works.
Now on to my own question. :-)
Steve, the one thing I'm not getting from the article, nor from the website (at least, I haven't seen it yet) is as follows: Is this just another DRMAA implementation, or is it more than that? If it is, could you give us a good overview of why it's better than N1? If not, can you explain what exactly this software does for a company? It somewhat sounds like it makes a single JVM run across multiple machines as if they were one, but if that's the case, how does it work? Is it a customized JVM based on Sun source code?
Thanks in advance! -
Basic idea of what this software is...
It's very similar to clustered J2EE application servers. With standard J2EE clustering you can group several machines together that all run a single application and spread clients between those systems though a round-robin approach(usually with sticky session) or new clients could be sent to the machine that is the least utilized. Currently with J2EE application server there isn't a whole lot of support for fine tuning client distribution with you own (performance/utilization) load balancing rules. That's where this software comes in, it looks like it adds in extra clustering features to Application Servers like BEA that can already be clustered(BEA is the only one supported at this point). I have nothing to do with these people, I'm a Java instructor and I spent 3 minutes looking at Cassatt's website. There seem to be some software cost justifications there too for those of you asking why it costs so much.