Closed fouvy closed 4 years ago
Hi @fouvy
The updated peach functionality introduced in kdb+ 4.0 relates to updated performance for kdb+ primitives only, this is explicitly outlined here
As such it would not be expected that the addition of distributed primitives in kdb+ 4.0 would have any impact on the speed of execution of any code on Python side as is the case in your example. These are two separate problems.
Stale issue message
Questions
[ ] Which operating system are you using (if Linux, please provide flavour of it, i.e RedHat, CentOS or Ubuntu), is it 32-bit, or 64-bit?
[ ] Which version of PyQ are you running? Please provide output of
pyq --versions
, if PyQ isn't operational, please provide Python interpreter version and PyQ versionpython -V; python3 -V; pip list | grep pyq
:[ ] Which version of kdb+ are you using, is it 32-bit or 64-bit?
[ ] If on 64-bit, is your
QLIC
set? Please provide outputenv | grep QLIC
on linux/macOS, orset|grep QLIC
on Windows.[ ] Did you use virtual environment to install PyQ? If not, why?
[ ] Where is your
QHOME
? Please provide outputenv | grep QHOME
on linux/macOS, orset|grep QHOME
on Windows.[ ] Do you use Conda? If so, what version?
Steps to reproduce the issue
Expected result
Actual result
Workaround
pyq doesn't run faster parallelly with kdb+ 4.0. This is my testbench.py file
Then I ran with my kdb+ like following:
I found that pyq cannot run faster when I testing code under kdb+ 4.0. I can run my code faster when I run peach with c library. I thought it might be kdb+ slave doesn't fork embedpy independently.