Hi Johann： So you mean that although the operation over SCM is fast， but several sequential operations over SCM may result in the high latency？ Here is the test in my server with

Hi, A DAOS update operation actually results in several sequential latency-sensitive operations over SCM to locate the object/dkey/akey (and create the associated trees if those don’t exist

Hi Johann: Tansks for the information. I have checked the latency in the online documentation, about 12 us for update, much lower than that in my test. But I think SCM would be much faster while the

Hi there, I don’t think that we have ever run any benchmarks with only 2x Optane DIMMs. Maybe you could start by running vos_perf and compare to the results we have in the online

Thansks for reponseing. And can you share your latency in you internal testing? Best Regards!

When I replied last week I forgot to mention, we do have a control API written in Go, which you could also use for this purpose:https://github.com/daos-stack/daos/tree/master/src/control/lib/control

You should use dmg storage format. As things stand, we don’t enable users to call the administrative gRPC methods directly. The API is internal and may change. Thanks, Kris

After services started, I'll format pmem and nvme (from code). Need to exec 'dmg storage format' or can call 'ctlpb.CtlSvcClient.StorageFormat'? Can I use dRPC for control daos_server? Or in the

Here is my HW configuration： CPU： Intel(R) Xeon(R) Gold 6248R CPU @ 3.00GHz SCM：2 SCM ，256GB I use array interface in this test and set the obj class to OC_RP_3GX. 32GB for hugepage

Might take a few days till I'm back working on that setup, but will update. As far as I remember, no output what so ever was printed though.

Omer, I’d be interested in seeing the stdout/stderr and logging from dfuse where this is happening. As you say the -f option should make it run in the foreground so if you’re not passing this

Hi, Thanks for your reply. 1. I saw :). Cool. 2. I used to build DAOS and install it, so I had a script that did that for me, but yes, with RPM based solution this shouldn't be a concern. I fixed my

Hi there, Thanks for reaching out. The online doc has been fixed and now specifies a different URL for CentOS7 and 8. /var/run/daos_agent should be automatically created after enabling/starting

Hi there, Could you please tell us more about your HW configuration and the test case (e.g. I/O size, read or write, object class, …)? We definitely see lower latency in our internal testing.

Some post DAOS 2.0 installation and comments and questions: 1. We use a mix of CentOS 7 and 8 in our setup. However, the DAOS online documentation at "https://docs.daos.io/v2.0/QSG/setup_centos/"

Hello everyone: Recently, I did some testing with daos array interface, found that after finishing nvme bio, it took me a long time for writing metadata and resource release ; The total latency of

Hi, In your example, the ULT will be tracked in the wait list from “ABT_future” on waiting, once it’s waked up, it’ll be pushed back to a runnable ULT FIFO list (per ABT pool, maintained

I’m not sure why the libraries aren’t being linked/loaded – maybe someone more knowledgeable on the DAOS team has an idea. The make command does include the libraries, and the libraries are

Yes, the same errors. daos_agent@sw2:~/git/mpifileutils/build$ export LD_LIBRARY_PATH=${MY_DAOS_INSTALL_PATH}/lib64:$LD_LIBRARY_PATH daos_agent@sw2:~/git/mpifileutils/build$ echo

Will you try appending ${MY_DAOS_INSTALL_PATH}/lib64 to your LD_LIBRARY_PATH and re-run the “make” command? export LD_LIBRARY_PATH=${MY_DAOS_INSTALL_PATH}/lib64:$LD_LIBRARY_PATH ~Dalton