Hi Sebastian, Thanks a lot for your reply. It was really helpful and it is clear that 'make check' don't start a ceph cluster. After your email I have figured it out. This brings me to another question :-) In my earlier email I should have defined what exactly I mean by 'workload' in my case. Given my current task/scenario, the definition of 'workload' is only the workload of client machine. Meaning, if there is a Ceph cluster, I am only concerned with the workload of a single ceph client node. And not the workload of other nodes that include OSDs, MONs, MDS etc. The question arises what exactly on ceph client? On client side, I would like to profile the workload of CRUSH. Because I am quite sure there are many computations in CRUSH that are compute intensive for CPU and can be offloaded. May be these compute intensive computations can be more parallelized. This is why I was profiling the binaries of unit tests (in particular CRUSH unit tests) on profiling tool Valgrind --tool=callgrind to see the function calls. May be this is not the right way? Please do comment on it :-). Considering my task, would you still recommend me to use Teuthology tests at this point? Please do comment on this also :-). Because integration tests (Teuthology framework) require multi-machine clusters to run. And according to my understanding that would be too complex for a single client workload or lets say if I am only interested in CRUSH workload. Thanks in advance :-) On Thu, May 7, 2020 at 12:20 AM Bobby <italienisch1987@gmail.com> wrote:
Hi Sebastian,
Thanks a lot for your reply. It was really helpful and it is clear that 'make check' don't start a ceph cluster. After your email I have figured it out. This brings me to another question :-)
In my earlier email I should have defined what exactly I mean by 'workload' in my case. Given my current task/scenario, the definition of 'workload' is only the workload of client machine. Meaning, if there is a Ceph cluster, I am only concerned with the workload of a single ceph client node. And not the workload of other nodes that include OSDs, MONs, MDS etc. The question arises what exactly on ceph client? On client side, I would like to profile the workload of CRUSH. Because I am quite sure there are many computations in CRUSH that are compute intensive for CPU and can be offloaded. May be these compute intensive computations can be more parallelized. This is why I was profiling the binaries of unit tests (in particular CRUSH unit tests) on profiling tool Valgrind --tool=callgrind to see the function calls. May be this is not the right way? Please do comment on it :-).
Considering my task, would you still recommend me to use Teuthology tests at this point? Please do comment on this also :-). Because integration tests (Teuthology framework) require multi-machine clusters to run. And according to my understanding that would be too complex for a single client workload or lets say if I am only interested in CRUSH workload.
Thanks in advance :-ยด)
Bobby
On Wed, May 6, 2020 at 5:37 PM Sebastian Wagner <sebastian.wagner@suse.com> wrote:
Hi Bobby,
`make check` aka unit tests don't start a ceph cluster. Instead they test individual functions. There is nothing similar to a "workload" involved here.
Maybe, you're interested in the vstart_runner, which makes it possible to run Teuthology tests in a vstart cluster.
Best,
Sebastian _______________________________________________ Dev mailing list -- dev@ceph.io To unsubscribe send an email to dev-leave@ceph.io