8000 About running workload YCSB-A/B/E · Issue #8 · SJTU-IPADS/xstore · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

About running workload YCSB-A/B/E #8

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you ag 8000 ree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
furtheranddeeper opened this issue Jul 18, 2022 · 4 comments
Open

About running workload YCSB-A/B/E #8

furtheranddeeper opened this issue Jul 18, 2022 · 4 comments

Comments

@furtheranddeeper
Copy link
furtheranddeeper commented Jul 18, 2022 •
edited
Loading

I setup the system and run workload YCSB-C/D successfully.
But when I tried to reproduce the YCSB-A/B/E results with the command from ./ae_scripts, it didn't work well.

  1. For YCSB-A/B:
    ./fserver -db_type ycsb --id 0 -ycsb_num=1000000 --no_train=false --step=2 --model_config=ae_scripts/ycsb-model.toml --threads 1
    ./ycsb -workloads ycsba -server_host 192.168.0.4 --id 1 -total_accts=1000000 -eval_type=sc --threads 1 -need_hash=false --cache_sz_m=327680 --eval_type=sc --concurrency=1 --undefok=concurrency,workloads,eval_type,total_accts,server_host,cache_sz_m,need_hash
    All logs that ./ycsb print show below. It print nothing after the last log in [clients.hpp:304].
    [mem_region.hpp:68] region manager alloc memory: 0x7f7576dff010
    [allocator_master.hpp:50] allocator master register memory: 2147483648
    [allocator_master.hpp:43] AllocatorMaster<0> inited multiple times
    [main.cc:121] 192.168.0.48888
    [main.cc:132] starting threads, using workload: ycsba
    [controler.hpp:28] controler main loop starts
    [rdma_ctrl.hpp:110] rdma ctrl started!
    [lib.hpp:43] fetch mr done
    [lib.hpp:50] create ud done
    [controler.hpp:118] controler start listening
    [clients.hpp:304] update second layer done using : 406277 msec

  2. For YCSB-E:
    ./fserver --id 0 -db_type dummy -ycsb_num 1000000 --model_config=ae_scripts/ycsb-dynamic-model.toml --threads 1
    ./micro -server_host 192.168.0.4 -id 1 -total_accts=1000000 --force_rpc=false --workloads=dynamic_scan --threads=1 --concurrency=1 --undefok=concurrency,force_rpc,threads,workloads,total_accts
    All logs that ./micro print show below.
    [mem_region.hpp:68] region manager alloc memory: 0x7fe7231ff010
    [allocator_master.hpp:50] allocator master register memory: 2147483648
    [allocator_master.hpp:43] AllocatorMaster<0> inited multiple times
    [dynamic_scan.hpp:27] client use dynamic changing workloads, V2
    [main.cc:295] starting 1 threads, using workload: dynamic_scan
    [main.cc:299] all threads start done
    [controler.hpp:28] micro controler main loop starts
    [rdma_ctrl.hpp:110] rdma ctrl started!
    [controler.hpp:40] memory regsiter done 75
    [lib.hpp:43] fetch mr done
    [lib.hpp:50] create ud done
    [controler.hpp:47] controler adapter done
    [controler.hpp:143] Micro controler starts.
    [dynamic_scan.hpp:478] start to bootstrap xcache!!!!!!!!!!!!!!!!!!
    [single_op.hpp:129] poll till completion error: 12 transport retry counter exceeded
    [seralize.hh:211] page entries: 0
    [seralize.hh:212] Assertion! seq: 0 0
    Aborted (core dumped)

  3. Did I run ./ycsb or ./micro with the right commands? What should I do to run YCSB-A/B/E?
@wxdwfc
Copy link
Collaborator
wxdwfc commented Jul 18, 2022

Hi I'm quite busy these days and will checkout these issues later in this week.

@furtheranddeeper
Copy link
Author

Hi I'm quite busy these days and will checkout these issues later in this week.

Thanks for your reply. I have run YCSB-A/B successfully with the same commands in YCSB-C scripts. Now the only problem existed is about YCSB-E.

@wxdwfc
Copy link
Collaborator
wxdwfc commented Jul 24, 2022

Hi, for how to run YCSB-E, you can check our scripts in ae_scripts/ycsbe.toml, which I think is quite self-explained:

  1. run fserver at the server-side and
  2. run ./micro at the client-side.

@furtheranddeeper
Copy link
Author

Hi, I have checked the script for YCSB-E and I just followed the commands in it.
At the server-side: ./fserver --threads 24 --id 0 -ycsb_num=20000 -db_type dummy -ycsb_num 20000000 --model_config=ae_scripts/ycsb-dynamic-model.toml
At the client-side: ./micro --threads 24 -concurrency 1 -workloads dynamic2 -server_host 192.168.0.4 -id 1 -total_accts=10000000 -need_hash=true -total_accts=20000000 --force_rpc=false --workloads=dynamic_scan --threads=24 --concurrency=1 --undefok=concurrency,force_rpc,threads,workloads,total_accts
However, it still meets [seralize.hh:212] Assertion! seq: 0 0 Aborted (core dumped) at the client-side.
I checked the assertion, it was defined in function extract_submodel_to and used in funcition get_model and boot_extract_model.
It seems that the assetion failed when client first get the xcache model.
Did I use the right commands? Or there is something wrong in xcache when doing YCSB-E workload?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@wxdwfc @furtheranddeeper
0