I will be using sockets for the client/server communicationYou will be using RMI or Corba for the client/server communication actually.
I am currently testing for, memory usage of the client application, average data throughput, total packets sent and lost and cpu times for both client and serverYou should also test latency
I'm still researching on the best possible way to conduct the test and would appreciate it if anyone could help me on what tools to use and ways to conduct this test, thanks...You could probably automate it using JMeter. Very handy thing. You can write both the client and the server in Java, using either RMI/IIOP or IDLJ for the Corba part. No particular reason not to use RMI/IIOP that I can see, it's just a thin layer over the other, more or less, and it's much easier to program.
Native RMI is much simpler than Corba, but it's much more rudimental.I assume you meant 'rudimentary'.
I think you can't only warry about performance and so on, a good Croba system, like Orbacus 4.3 or Jacorb 3.1, offers you a lot of functionalities obviously not permitted by RMI.But his question is about performance measurement.
In my opinion, on a LAN Corba is still a good choiceYou're ten weeks late with that unsolicited opinion.