The SS engine only accesses the second processor when the engine is running... so... start playback and you should see dual activity.
It splits all display and disk access to one cpu and keeps the entire MT loop and driver access on the second.
I found this to be the best method for the highest performance... others may argue differently... but the results are what I gauge by.
VST and DX plugs mostly process in floating point, so adding them into the loop starts to defeat the idea of keeping the purity of the integer math engine at the forefront... most of the good native plugins have tried to maintain the integer format where possible.
Even I broke from the integer for a small portion of the built-in eq code, but when I do, I use hand coded floating point assembly language and never rely on compilers to make my final code image decisions for me... I pay very close attention to the instructions and the order used to minimize or remove the floating point issues that cause problems. There are many optimization gurus out there who could even take my code much further and optimize for specific cpu pipeline architectures and so forth, but in general, my code has been known to attain extremely high performance on most machines it encounters.
Have fun with your experimentations... listen to the results... learn the interface and watch my demo videos online for an idea how things should look to you as you move around in the program.
Good Luck,
Bob L
It splits all display and disk access to one cpu and keeps the entire MT loop and driver access on the second.
I found this to be the best method for the highest performance... others may argue differently... but the results are what I gauge by.
VST and DX plugs mostly process in floating point, so adding them into the loop starts to defeat the idea of keeping the purity of the integer math engine at the forefront... most of the good native plugins have tried to maintain the integer format where possible.
Even I broke from the integer for a small portion of the built-in eq code, but when I do, I use hand coded floating point assembly language and never rely on compilers to make my final code image decisions for me... I pay very close attention to the instructions and the order used to minimize or remove the floating point issues that cause problems. There are many optimization gurus out there who could even take my code much further and optimize for specific cpu pipeline architectures and so forth, but in general, my code has been known to attain extremely high performance on most machines it encounters.
Have fun with your experimentations... listen to the results... learn the interface and watch my demo videos online for an idea how things should look to you as you move around in the program.
Good Luck,
Bob L
To be honest... I am seeing lower loads when forcing to one cpu... the dual context switching on all the driver threads... especially for MME.... one thread per device... randomly being assigned to different processors on the fly... things get real complicated... at very low latencies, the cpu switching time can actually cost performance speed because everything is happening in less than a ms... so be aware... more cpus does not necessarily mean higher performance. In the case of SAC and SS on a dual... I would probably try keeping SAC on one cpu and SS on the other... this would have be done in the task manager. Bob L
從BOB的觀察當中, 可以知道 多CPU 不代表一定有高效能的表現, CPU的切換往往影響工作速度, 把工作放在單CPU上在現階段仍有不錯的表現。
現時在雙CPU的情況下, SAW 是把 MT 的循環放在 第2顆 CPU運行, 而第一顆 CPU 負責 顯示 和 硬盤的寫和讀; SAW 和 SAC 同時運行的話, 它們也將會分別被安排到兩顆 CPU 工作。
其實在國外論壇也看到很多 8 CORE 的機器 跟第三方軟件有不兼容的問題出現, 不過多核心將會是主流, 就等它盡快成熟, 那麼一天我們就能真正享受其優勢.......
從BOB的觀察當中, 可以知道 多CPU 不代表一定有高效能的表現, CPU的切換往往影響工作速度, 把工作放在單CPU上在現階段仍有不錯的表現。
現時在雙CPU的情況下, SAW 是把 MT 的循環放在 第2顆 CPU運行, 而第一顆 CPU 負責 顯示 和 硬盤的寫和讀; SAW 和 SAC 同時運行的話, 它們也將會分別被安排到兩顆 CPU 工作。
其實在國外論壇也看到很多 8 CORE 的機器 跟第三方軟件有不兼容的問題出現, 不過多核心將會是主流, 就等它盡快成熟, 那麼一天我們就能真正享受其優勢.......
再來一段...
Trust me... dual cores are voodoo.... I am seeing some things that you really do not want to see in the way the processor scheduling works... in realtime critical apps... like SAWStudio and especially SAC... it is quite a horror story when you get down deep to cpu and thread context switching at less than 1 ms increments.... many delays and flat-out bizzarre issues that crop up from machine to machine... from service thread to service thread... from one driver to the next... just from whether the task manager or something like it is running at the same time or not.... it is quite the journey trying to lock it all down... and for what... not very much, if any performance gains... in many cases performance losses... and a definite attack on overall stability.
The exact same code will fail on my hyperthreaded cpu and work perfect on my true dual core... load has no bearing... the hyperthread causes some very real issues in and outside my code that throws the critical timing for a spin... perfectly demonstartable... in fact... I can have total distortion and buffer slippage happening on the hyperthread and then switch to the single cpu option, on the fly without even stopping the engine, and the audio clears up perfectly, instantaneously...
I am working hard on it.... but believe me.... a single cpu is a much more stable beast, with no question about it, in my opinion.![]()
Bob L
Trust me... dual cores are voodoo.... I am seeing some things that you really do not want to see in the way the processor scheduling works... in realtime critical apps... like SAWStudio and especially SAC... it is quite a horror story when you get down deep to cpu and thread context switching at less than 1 ms increments.... many delays and flat-out bizzarre issues that crop up from machine to machine... from service thread to service thread... from one driver to the next... just from whether the task manager or something like it is running at the same time or not.... it is quite the journey trying to lock it all down... and for what... not very much, if any performance gains... in many cases performance losses... and a definite attack on overall stability.
The exact same code will fail on my hyperthreaded cpu and work perfect on my true dual core... load has no bearing... the hyperthread causes some very real issues in and outside my code that throws the critical timing for a spin... perfectly demonstartable... in fact... I can have total distortion and buffer slippage happening on the hyperthread and then switch to the single cpu option, on the fly without even stopping the engine, and the audio clears up perfectly, instantaneously...
I am working hard on it.... but believe me.... a single cpu is a much more stable beast, with no question about it, in my opinion.
Bob L
另一位SAW用戶.......
SAwstudio is written for dualcore systems, and I beleive SAC is as well. So I dont think that having a specific change to the code would help things work better... The way dual-core and dual-processor systems work simply causes issues with all software.
The only audio program I've seen that has a great benefit from dual-cores is Podium, and the author has done some rather awesome things on that front... and IIRC even he recommends single core given the same available IPS.
I've been told that Sonar uses dual-core systems well, but I've also seen plenty of proof on their own forums that it causes trouble too.
__________________
Lovingly signed,
Robert Randolph
SAwstudio is written for dualcore systems, and I beleive SAC is as well. So I dont think that having a specific change to the code would help things work better... The way dual-core and dual-processor systems work simply causes issues with all software.
The only audio program I've seen that has a great benefit from dual-cores is Podium, and the author has done some rather awesome things on that front... and IIRC even he recommends single core given the same available IPS.
I've been told that Sonar uses dual-core systems well, but I've also seen plenty of proof on their own forums that it causes trouble too.
__________________
Lovingly signed,
Robert Randolph
翻一翻樓上的...
sawstudio 是支持雙核, sac 也是, 故此改動編程也不會有大幫助, 其實很簡單, 很多時候是雙核的工作方式導致軟件出現問題...
我見過唯一能取得雙核優點的音頻軟件是 Podium, 開發者前期確下了不少功夫, 但他也推薦單核也能達到同樣效果.....
有人告訴我 sonar支持雙核, 但在sonar論壇經常看到很多問題的發生....
----------------------------------------------------------------------------------------------------------------------
這位人兄也曾參與過一些公司破解自己產品的工作.......也認識破解組織朋友, 他說 上一代破解組織有個共識, 為了專重bob在軟件上的才華和貢獻, 他們不去碰 sawstudio...
[ 本帖最后由 himhui 于 08-9-5 23:08 编辑 ]
sawstudio 是支持雙核, sac 也是, 故此改動編程也不會有大幫助, 其實很簡單, 很多時候是雙核的工作方式導致軟件出現問題...
我見過唯一能取得雙核優點的音頻軟件是 Podium, 開發者前期確下了不少功夫, 但他也推薦單核也能達到同樣效果.....
有人告訴我 sonar支持雙核, 但在sonar論壇經常看到很多問題的發生....
----------------------------------------------------------------------------------------------------------------------
這位人兄也曾參與過一些公司破解自己產品的工作.......也認識破解組織朋友, 他說 上一代破解組織有個共識, 為了專重bob在軟件上的才華和貢獻, 他們不去碰 sawstudio...
[ 本帖最后由 himhui 于 08-9-5 23:08 编辑 ]
