Overhead and Best Practices

IKVM with Drools 2.x has been a great success. We are now looking to do 
something similar for Drools 3.0. However we are under pressure for a 
full port of the core code - which I want to resist due to the resources 
needed to maintain such an effort.

One key issue that .Net developers bring up is the overhead of using 
IKVM - quoting figures of over 20%. I have no empiracal facts, but I 
find that hard to be true. Anyway it would be good if IKVM developers 
could provide some empircal information and also best practices - i.e. 
things to avoid if you want speed. Then I can say we are using IKVM 
overhead for X is no more than 3%, overhead for Y is 5%, we avoid Z 
which is 20%. If the overhead is only a few percent and IKVM  continues 
to prove stable, as it already has done, the case for a native port 
diminishes.

Also maybe a "Get the Facts" document might help, as i have some users 
worred about a Frankenstein system; even though I tell them that running 
Java on .Net is no different than runny Python or VB, it all compiles 
down to IL.

Mark



-------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642