WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

[Xen-devel] JavaRMI and Xen problem

To: <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-devel] JavaRMI and Xen problem
From: "Dharanikota, Sai" <sai.dharanikota@xxxxxxxxx>
Date: Tue, 26 Apr 2005 15:50:15 +0200
Delivery-date: Tue, 26 Apr 2005 13:50:36 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcVKZt+v+T1Ezw47QWuRqRg3+tMl9g==
Thread-topic: JavaRMI and Xen problem

Hello,

 

I am facing a strange problem with Java RMI and Xen. I will describe the problem as well as the experimental results.

 

Setup:

 

I have taken 2 machines, machine1 and machine2. Machine1 is the client and Machine2 is the server. The RMI registry is available on Machine2. I have a RMI application (a kind of service) that is running on Machine2 on port 4001. An init script starts the service at boot time on port 4001.

 

Scenario1: Machine2 is booted with xen as the kernel

The client on Machine1 tries to look up the object that it needs to contact in the registry on Machine2. The object to be available in the RMI registry on Machine2 takes around 2 minutes.

 

Scenario2: Machine2 is booted with Linux kernel (Xen is not involved at all)

The client on Machine1 tries to look up the object that it needs to contact in the registry on Machine2. The object to be available in the RMI registry on Machine2 takes around 21 seconds.

 

In scenario1 I am not starting any virtual machines. The service is available in Domain0 (Machine2). Nothing is changed except the kernel to boot. But, the results look strange. The Xen and Java RMI stuff looks very strange. The problem here is, on a Xen machine the Java object to be available in the RMI registry takes very long time. According to our experiments it shows that it is approximately 6 times slow. Is it normal with RMI-Xen?

Can any body give pointers to this problem?

 

Thanks,

Sai

 

 

Sai S. Dharanikota

Intel GmbH

Software & Solutions Group

Hermuelheimer Strasse 8a

50321 Bruehl

Germany

Tel : +49 2232 209053

 

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
<Prev in Thread] Current Thread [Next in Thread>