On Friday 10 October 2003 11:18 am, Chris Cannam wrote: > Now I'm guessing that the problem is just that the GUI's being > swamped with DCOP setPointerPosition calls, which the sequencer > appears to be sending every 5ms (200 per sec! do I have this > right?) from its updateClocks() method.
Hang on though - these have always been sent long before we moved to mmap. I would suggest (on first thoughts) that there's something else in the GUI taking up the time. Why don't you use cachegrind to try and locate it? I would be surprised if this very old code has anything to do with the issue but I would definitely advise (nay insist) you characterise it before poking around with code. 200 DCOP async "send"s per second isn't really that many after all. That whole sync relationship could be better but I don't think that's the issue here. Much more likely to be something that the gui is doing slowly on to update I would imagine. I'll try a cachegrind run this afternoon. _Do_ download it and get used to it. It's easy - it helps - and "touch cachegrind.cmd" is your friend. R ------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. SourceForge.net hosts over 70,000 Open Source Projects. See the people who have HELPED US provide better services: Click here: http://sourceforge.net/supporters.php _______________________________________________ Rosegarden-devel mailing list [EMAIL PROTECTED] - use the link below to unsubscribe https://lists.sourceforge.net/lists/listinfo/rosegarden-devel
