Are you pip installing from pypi or are you building your own client package to install (https://github.com/Bears-R-Us/arkouda#install-ak).
You shouldn't install from pypi as we have not updated that in quite some time and it will not work with the current server.
hi all - new to this project. i have just been playing with arkouda for the past month or so.
i am having an issue with using a system where 256 threads are available (2 x 64 core processors with hyperthreading) and am only getting 128ish arkouda threads. how is the number of arkouda threads spun up decided for a given system? it seems there is a default value that applies to smaller machines but not this machine i am trying. Is there a max number of threads? Is there a flag to specify how many threads to spin up when starting the server? Thanks!
CHPL_RT_NUM_THREADS_PER_LOCALE, but generally speaking using logical threads will not help performance and may in fact hurt. See https://chapel-lang.org/docs/usingchapel/tasks.html#controlling-the-number-of-threads for more info.
I'm fairly certain the reason for hanging/failure was the server process dying and the client ZMQ socket waiting for reconnection. If that's the case the test will never actually complete and should be considered failed as soon as the server process dies.
However, if you want to try to increase the time out you can install the
pytest-timeout plugin and it enables the cmd line arg
--timeout=300 where the value is in seconds. An alternative is to try and use pytest marks to set something on a specific test
@pytest.mark.timeout(10, "slow", method-"thread") (from the pytest docs)
Michael Merrill is inviting you to a scheduled Zoom meeting.
Topic: Arkouda Weekly Zoom Meeting Time: recurring meeting Tuesdays @ 1pm ET
Meeting ID: 777 1700 0423 Passcode: kjM3WS
During your first run you should have gotten a message from gasnet recommending a value for
GASNET_PHYSMEM_MAX. This is usually ~2/3 of physical memory or a limit set by the HCA. This limits how much memory can be pinned, but not how much physical memory you can allocate (just how much can be pinned / communicated at any given time).
The amount the server reports comes from https://chapel-lang.org/docs/modules/standard/Memory/Diagnostics.html#Diagnostics.locale.physicalMemory, which should just be the physical memory of a system. Can you run
free -g on the nodes to verify the OS reports ~750G and not ~512G?