Add a comment

 

Re: Component Deployment

I like what you're saying. I once got bitten by a threading problem in apache axis 1.4 (ish) Short version is, in test we were on a Solaris T2000, and in production a v490 In theory the boxes have roughly equivalent performance unless you're doing floating point (which we weren't) but if you were, the v490 is much better. Turns out the timeslicing on the CPUs is rather different, so on a v490 a hardware thread gets swapped in and stays in for a lot of work, whereas a T2000 has way more hardware threads but each thread does a lot less before getting swapped out. Upshot was on a t2000 (ie our test box) it was exceedingly difficult to reproduce the issue. but on a v490 (production) they were 10 a penny. Lots more analysis and testing revealed certain roughly equivalent CPU were 16 times more likely to exhibit the same thread problem than others, despite the insulation you might think the JVM gives you The lessons learnt about same kit in production/test are obvious But the lessons learn on the risk of having different kit, and how to mitigate the risk are a bit more subtle - and explaining all this to the service manager was somewhat challenging! disclaimer: I cant remember which way round v490, T2000 and x86 (xeons) were

Re: Component Deployment


Title
Body
HTML : b, strong, i, em, blockquote, br, p, pre, a href="", ul, ol, li, sub, sup
Name
E-mail address
Website
Remember me Yes  No 

E-mail addresses are not publicly displayed, so please only leave your e-mail address if you would like to be notified when new comments are added to this blog entry (you can opt-out later).