Marc Siegel wrote:
Have you sent this to the ORBit2 list? All the marshalling, GIOP, and so on is done in ORBit2 (C code). The wrapper layer for orbitcpp does introduce inefficiency (converting C++ types into C types, some memory allocation, ...) but it should be fairly predictable (aside from maybe the memory allocation/deallocation) and there is no difference in the wrapper between asynchronous and synchoronous.Sorry for the reposting there.
No, I haven't seen this before. But I don't use one-way much and I haven't been doing serious profiling of the project I use ORBit2 for. If you can supply profile data indicating inefficiencies in the orbitcpp wrapper, I can look at fixing that. But I suspect that isn't what is causing the problem.Marc On Thu, 2004-07-22 at 15:54, Marc Siegel wrote:Hi, I've been doing some benchmarking of open-source CORBA ORBs at work, and have come across the odd result that even in the local case, asynchronous (one-way) invocations of calls often take much longer than the synchronous counterpart, with a huge variability in latency and jitter results across test runs. I'll be happy to share more details, but I am mainly interested if anyone has heard of this before, and if anyone has any ideas why I am getting these results based on prior experience.
-- Bowie Owens CSIRO Mathematical & Information Sciences phone : +61 3 9545 8055 fax : +61 3 9545 8080 mobile : 0425 729 875 email : Bowie Owens csiro au