Here is my first attempt on profiling the SFZ engine as you recommended, using Oprofile and the settings you mentioned. This was done with the default setting of LS, i.e. 64 voice polyphony and 90 max voices.
After the profiling, I get the following report ```CPU: AMD64 family15h, speed 2100 MHz (estimated) Counted CPU_CLK_UNHALTED events (CPU Clocks not Halted) with a unit mask of 0x00 (No unit mask) count 100000 CPU_CLK_UNHALT...| samples| %| ------------------ 2857302 99.9834 bash CPU_CLK_UNHALT...| samples| %| ------------------ 2112992 73.9506 liblinuxsampler.so.5.0.0 602207 21.0761 kallsyms 49469 1.7313 libjack.so.0.1.0 49023 1.7157 libc-2.31.so 14103 0.4936 libstdc++.so.6.0.28 11851 0.4148 libsndfile.so.1.0.28 5947 0.2081 [vdso] (tgid:74493 range:0x7ffc0e633000-0x7ffc0e633fff) 5729 0.2005 ext4 3855 0.1349 libpthread-2.31.so 1676 0.0587 libm-2.31.so 266 0.0093 ld-2.31.so 77 0.0027 kvm 42 0.0015 bash 30 0.0010 lt-linuxsampler 24 8.4e-04 libgcc_s.so.1 3 1.0e-04 jbd2 2 7.0e-05 libdb-5.3.so 2 7.0e-05 libmvec-2.31.so 1 3.5e-05 filter.so 1 3.5e-05 libncursesw.so.6.2 1 3.5e-05 libreadline.so.8.0 1 3.5e-05 librt-2.31.so 317 0.0111 sed CPU_CLK_UNHALT...| samples| %| ------------------ 212 66.8770 libc-2.31.so 88 27.7603 kallsyms 14 4.4164 ld-2.31.so 3 0.9464 sed 156 0.0055 ls CPU_CLK_UNHALT...| samples| %| ------------------ 77 49.3590 libc-2.31.so 66 42.3077 kallsyms 11 7.0513 ld-2.31.so 2 1.2821 ls ``` I also got messages from LinuxSampler on the terminal occasionally: ```DiskThread: there was no free slot Disk stream order failed! EngineBase: ERROR, voice stealing didn't work out! DiskThread: there was no free slot Disk stream order failed! EngineBase: ERROR, voice stealing didn't work out! DiskThread: there was no free slot Disk stream order failed! EngineBase: ERROR, voice stealing didn't work out! DiskThread: there was no free slot Disk stream order failed! EngineBase: ERROR, voice stealing didn't work out! ``` Best, Ebad On Friday, April 10, 2020, 11:34:40 AM GMT+2, Christian Schoenebeck <schoeneb...@linuxsampler.org> wrote: On Donnerstag, 9. April 2020 16:12:42 CEST joo bian wrote: > I can gladly generate the profiling for you guys, as I really wish for this > problem to be solved as soon as possible. Do you have some suggestions for > how to go about the profiling? In the linuxsampler configuration there are > some arguments for detailed logging and debugging. Should I activate them? Profiling is done by using an external development tool. That's not a built-in feature of the sampler. There are numerous profilers out there now. IMO e.g. OProfile was always a good choice on Linux. There are various good howtos on the Internet how to perform profiling with the profiler of your choice. Just keep in mind that before you start profiling, the sampler must be compiled with debugging symbols turned on, which means additionally to the -O3 flag you also have to add the -g flag. Also: the sampler's binary must not be stripped after compilation, which e.g. the Debian packaging scripts would do by default, because stripping removes the debugging symbols from the binary again. For that reason I recommend you to not even bother to install the sampler in this case, just type CXXFLAGS="-O3 -g" ./configure && make from the source file directory to compile it, then simply run the sampler with src/linuxsampler CU Christian _______________________________________________ Linuxsampler-devel mailing list Linuxsampler-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxsampler-devel
_______________________________________________ Linuxsampler-devel mailing list Linuxsampler-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxsampler-devel
