Hi David,<br><br>The performances of XQuartz and Apple's X11 were very different on OS X 10.5 but I didn't noticed the same "gap" on OS X 10.6.<br>For my problem with the Logitech mouses I tried XQuartz 2.5.0 (there is a 2.5.2 release now ^^) and it didn't change the bugged behavior. It's very likely a driver issue. <br>
<br>Thanks a lot,<br>Rafael.<br><br><div class="gmail_quote">2010/7/26 David Gobbi <span dir="ltr"><<a href="mailto:david.gobbi@gmail.com">david.gobbi@gmail.com</a>></span><br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
If you are using the stock X11, you should replace it with xquartz<br>
2.5.x if you can. I've found that the stock X11 for OS X 10.6 will<br>
often start eating CPU for no apparent reason.<br>
<font color="#888888"><br>
David<br>
</font><div><div></div><div class="h5"><br>
<br>
On Mon, Jul 26, 2010 at 11:05 AM, Frava <<a href="mailto:fravadona@gmail.com">fravadona@gmail.com</a>> wrote:<br>
> Oh yeah you're too right !!! The main performance issue was due to the kind<br>
> of the mouse plugged on the workstation(s). The Logitech MX-Revolution<br>
> M-RBQ124 has a third button that eat all a CPU core when using it with X11<br>
> (and Python VTK). I think there could be another performance problem because<br>
> my test is running a little slow in this kind of MacPro, so I'll try Shark<br>
> as you advised me ;)<br>
><br>
> Thank you for the help,<br>
> Rafael.<br>
><br>
><br>
> 2010/7/26 Sean McBride <<a href="mailto:sean@rogue-research.com">sean@rogue-research.com</a>><br>
>><br>
>> On Mon, 26 Jul 2010 13:27:05 +0200, Frava said:<br>
>><br>
>> >My software works correctly on all GeForce workstations, but on Quadro<br>
>> >workstations it has a very slow execution when doing some graphical<br>
>> >movement... It's like it doesn't use the GPU acceleration (100% of one<br>
>> > CPU<br>
>> >core compared to 10% on other workstations).<br>
>> ><br>
>> >Could it be a hardware optimisation problem ?<br>
>><br>
>> It could be lots of things. You could measure what the CPU is doing by<br>
>> using Instruments or Shark.<br>
>><br>
>> --<br>
>> ____________________________________________________________<br>
>> Sean McBride, B. Eng <a href="mailto:sean@rogue-research.com">sean@rogue-research.com</a><br>
>> Rogue Research <a href="http://www.rogue-research.com" target="_blank">www.rogue-research.com</a><br>
>> Mac Software Developer Montréal, Québec, Canada<br>
>><br>
>><br>
><br>
><br>
</div></div><div><div></div><div class="h5">> _______________________________________________<br>
> Powered by <a href="http://www.kitware.com" target="_blank">www.kitware.com</a><br>
><br>
> Visit other Kitware open-source projects at<br>
> <a href="http://www.kitware.com/opensource/opensource.html" target="_blank">http://www.kitware.com/opensource/opensource.html</a><br>
><br>
> Please keep messages on-topic and check the VTK FAQ at:<br>
> <a href="http://www.vtk.org/Wiki/VTK_FAQ" target="_blank">http://www.vtk.org/Wiki/VTK_FAQ</a><br>
><br>
> Follow this link to subscribe/unsubscribe:<br>
> <a href="http://www.vtk.org/mailman/listinfo/vtkusers" target="_blank">http://www.vtk.org/mailman/listinfo/vtkusers</a><br>
><br>
><br>
</div></div></blockquote></div><br>