| I just tried csound5 with one of our gig set ups, so it was at about
70-80% cpu on an AMD 3000+, with ksmp=100.
The good news is, everything is working. So far the only build we've
been able to run ensembles that big on has been the varga build on
linux. For some reason after they got to a certain size they just
stopped working properly on CsoundAV. Never could figure out why.
Bad news is that it really isn't as performance solid as the Varga build
of 4.23.24 For whatever reason, it seems like the --sched option isn't
really doing much. On varga build, if we use --sched running as root,
csound takes control of *everything*. Meaning if we stay under 90% cpu,
we have no problems from printed output about midi allocation crap for
crap or mouses moving over xwindows etc. If we went about 100% cpu, the
entire system would go to it's knees and we'd have to reboot with the
power button, but under that was rock solid.
On csound5, printed output and mouse movements noticeably screw up the
audio even when running as root with --sched, cpu under 70%, and latency
set pretty high ( -b1024, about 20 ms ). Hope this is useful info to
someone! Hitting the sack now ( yeah I said that hours ago! ) but if
anyone has any tips I can try more benchmarks tomorrow.
Thanks
iain
-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net |