You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Although the core Java code is platform-independent, current Dike still relies on several shell scripts to schedule the benchmark process. It's a good idea to rewrite relative shell code into Python to enable Dike client to run on Windows.
Dike does not provide a user-friendly interface to operate with multiple clients. Deploying Dike on remote clients, and collecting and integrating results from them require lots of manual work. Aforementioned Python clients should do this work for users.
Fault injections should be separated from workloads if multiple clients work at the same time. Maybe we need a centralized scheduler to further control all benchmark components.