From: Paul N. <Pau...@Su...> - 2006-10-29 20:56:56
|
Hi Brian, You were spot on, it was that we had 256*1024 MTU size in the config file, which would be OK if we had IB set up, but needed to be reduced for GbE. Many thanks, Paul. Brian Paul wrote: > Paul Needle wrote: >> Thanks Brian for your response. >> >> We put together a DMX config today and used the render_to_app_window >> as part of the dmx.conf, which solved point 1. However, we now have >> an issue where the app hangs for about 5 seconds and then works fine >> for about another 5 seconds, then hangs again, etc. It could be to do >> with using GbE, as we are waiting for Infiniband switches, etc. >> However, what doesn't seem to add up is that when running VMD over >> DMX (app on master, rendered on slave) and not Chromium, we get good >> performance, however, once you put Chromium into the mix, the >> performance issues outlined above occur. >> >> Any pointers as to how to best debug what is going on would be much >> appreciated. > > Hmmm, that's weird. I'd probably run with gdb, interupt the program > during one of the pauses, and see where I am, then maybe add some > instrumentation to see where the time is going. > > Might also experiment with a smaller/larger MTU in the .conf file. > > -Brian |