Re: [Resin-interest] Resin on multiple CPUs
I ran into a similar problem,
On an older version of Resin, the performance was not what I expected from a
dual cpu. By creating two instances of Resin and under Windows, tying each
one to a cpu by setting the affinity, we were able to get the performance I
had expected. I thought I had heard that the latest JDK's had fixes for some
of these issues.
MC
-Original Message-
From: resin-interest-boun...@caucho.com
[mailto:resin-interest-boun...@caucho.com]on Behalf Of Mattias Jiderhamn
Sent: Tuesday, March 17, 2009 4:08 AM
To: Resin
Subject: [Resin-interest] Resin on multiple CPUs
Is there anyone that is running Resin on multiple CPUs that could tell
me if you did some special configuration to get this going?
We are currently running Resin 3.1.8 under Red Hat Enterprise Linux 5.3
and we are evaluating using multi CPU servers for running Resin, but it
just doesn't work.
When running standalone Java applications we get multi CPU use,
confirmed with both sar and the test class below. When running the
same test (in a JSP) under Resin only one CPU is used.
Why??? Is there some additional configuration we have to do?
(It shouldn't be a licensing issue since we have a 4 CPU evaluation license)
import java.lang.management.*;
import java.util.concurrent.CountDownLatch;
import java.util.concurrent.atomic.AtomicLong;
public class MultiCoreTester {
private static final int THREADS = 8;
private static CountDownLatch ct = new CountDownLatch(THREADS);
private static AtomicLong total = new AtomicLong();
public static void main(String[] args) throws InterruptedException {
long elapsedTime = System.nanoTime();
for (int i = 0; i THREADS; i++) {
Thread thread = new Thread() {
public void run() {
total.addAndGet(measureThreadCpuTime());
ct.countDown();
}
};
thread.start();
}
ct.await();
elapsedTime = System.nanoTime() - elapsedTime;
System.out.println(Total elapsed time + elapsedTime);
System.out.println(Total thread CPU time + total.get());
double factor = total.get();
factor /= elapsedTime;
System.out.printf(Factor: %.2f%n, factor);
}
private static long measureThreadCpuTime() {
ThreadMXBean tm = ManagementFactory.getThreadMXBean();
long cpuTime = tm.getCurrentThreadCpuTime();
double junk = 1;
for (int j = 0; j 18; j++) {
for (int i = 0; i 10 * 1000 * 1000; i++) {
// keep ourselves busy for a while ...
junk = junk + i-i;
}
}
System.out.println(junk = + junk);
cpuTime = tm.getCurrentThreadCpuTime() - cpuTime;
System.out.println(Thread.currentThread() + : cpuTime = + cpuTime);
return cpuTime;
}
}
--
/Mattias
___
resin-interest mailing list
resin-interest@caucho.com
http://maillist.caucho.com/mailman/listinfo/resin-interest
No virus found in this incoming message.
Checked by AVG - www.avg.com
Version: 8.0.237 / Virus Database: 270.11.15/2004 - Release Date: 03/16/09
07:04:00
___
resin-interest mailing list
resin-interest@caucho.com
http://maillist.caucho.com/mailman/listinfo/resin-interest
Re: [Resin-interest] resin-interest Digest, Vol 27, Issue 6
Emil, I worked with a startup recently that was doing php. There were having issues needing some serious server processing capacity. My recommendation was to use Quercus to leverage their code base. In the end, the php'ers were fired and .net folks brought in for a complete rewrite, what a shame. My point is, I think you guys have a great product, its just there is a real awareness issue (or prejudice) within the php community. Mica Cooper -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Emil Ong Sent: Sunday, September 07, 2008 6:26 PM To: Heimo Laukkanen Cc: resin-interest@caucho.com Subject: Re: [Resin-interest] resin-interest Digest, Vol 27, Issue 6 On Sun, Sep 07, 2008 at 04:17:51PM +0300, Heimo Laukkanen wrote: It would be great if Caucho could convince people from some of the php frameworks to work with you and test their frameworks on top of Quercus runtime besides just working with mod_php. It could be a good win-win situation for all the parties and also a way into the enterprise market for some of the frameworks. Currently I'm testing the code igniter framework - as our project is based on it - but will some day try to do something also with Zend framework, as it has a better featureset inside the framework itself and has commercial backing from the Zend corporation. We have been trying to do that, but there's been some resistance and hesistance so far. I think a lot of PHP people don't yet see what Quercus and running on a Java platform can offer them. Some just don't want to spend the time to change over, which is understandable. Java folks are much more excited. I recently gave a talk at the WordCamp in San Francisco (WordPress's conference for users and developers) and a lot of people were just confused by the concept at all. There are tons of smart people in the PHP world, we just need to get them looking at Quercus more seriously. If Quercus users would blog, post, and talk about it more, especially with success stories, I think that would go a long way in making that happen. I think Nam just fixed one of the Code Igniter bugs that you brought up earlier and we'd be happy to hear about any more that you run into. The nice thing about fixing bugs for one PHP application or framework is that it's likely to fix a bunch of others. I'm pretty sure we don't have the complete Zend Framework going as of yet, mainly because it uses the SPL extensively and we've only got about 25% done. Thanks, Emil Emil Ong Chief Evangelist Caucho Technology, Inc. Tel. (858) 456-0300 mailto:[EMAIL PROTECTED] http://blog.caucho.com/ Caucho: Reliable Open Source -- Resin: application server -- Quercus: PHP in Java -- Hessian Web Services ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest No virus found in this incoming message. Checked by AVG - http://www.avg.com Version: 8.0.169 / Virus Database: 270.6.16/1653 - Release Date: 9/6/2008 8:07 PM ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
Re: [Resin-interest] Websphere?
I switched several users of Webshpere over to Resin and never looked back. I would guess whatever your business reasons are for the change, they are not valid. It has also been my experience that Resin is faster, lighter, easier to manage, and Scott Ferguson as good as anyone left at the sinking ship that is BEA. Back in the day, BEA had some real talent (and they needed it to keep the beast from self-destructing). I don't see it anymore. Mica -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Haluk AKIN Sent: Friday, June 27, 2008 9:41 AM To: resin-interest@caucho.com Subject: [Resin-interest] Websphere? Hi, We are evaluating to switch our website from Resin to Websphere. I would appreciate if you could guide me to some comparisons between these two. Personal thoughts are welcome as well. Thanks, Haluk Akin ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
[Resin-interest] Resin 2.1.7 and JNDI
More info on this... It is supposed to be connecting to localhost:1099 but there is no open 1099 port. How is the 1099 port supposed to be opened?___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
Re: [Resin-interest] Resin 2.1.7 and JNDI
Ahhh ha, My example config is several years old but it has the JNDI example. I was looking at the Resin 2.1.17 libs and see no instance of the com.caucho.resources.rmi.RmiRegistry. Putting the rmi start into web-app causes an error...unknown element resource I guess that it has never work for 2.x? Mica -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Scott Ferguson Sent: Thursday, November 16, 2006 10:45 AM To: General Discussion for the Resin application server Subject: Re: [Resin-interest] Resin 2.1.7 and JNDI On Nov 16, 2006, at 5:52 AM, Mica Cooper wrote: More info on this... It is supposed to be connecting to localhost:1099 but there is no open 1099 port. How is the 1099 port supposed to be opened? This isn't really a Resin issue, it's a RMI issue. 1099 is the RMI registry. You would need to startup an instance of rmiregistry to make this work. -- Scott ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
