emery@xxxxxxx: Jens Axboe <axboe@xxxxxxxxx> In message <50A3DE92.3020509@xxxxxxxxx>, Jens Axboe writes: >On 2012-11-14 10:54, Jens Axboe wrote: >> On 2012-11-14 10:42, Jens Axboe wrote: >>>> For a while it was totting things up after four clients, >>>> which kind of made sense... now it's stuck on three. Back when >>>> it made more sense I thought that maybe handle_ts only dealt with >>>> the information from a single thread for each client rather than >>>> the aggregate of multiple thread jobs. That part seems to hold >>>> true even when it doesn't have the info for all the clients. >>>> >>>> Is this reporting the aggregate as expected? >>>> Is there a parameter change that I need to make to get >>>> the output I expect? >>> >>> As the job file is written, it will not aggregate results from a single >>> "instance" of the server. You would want group_reporting=1 to do that. >>> However, that will still give you one set of outputs per connection, not >>> one for all of them. Right now fio does not support collecting outputs >>> from all connections, a higher level group reporting if you will. >> >> Actually, I misremembered that and didn't check before replying. It >> _will_ sum all clients, if it has more than one connection. But there's >> a bug where we race on client exit and dec the expected client count. >> Does it work better with the below patch? > >Note that you still need group_reporting=1 in your job file, the all >clients report depend on getting only one set of stats from each client. >I'll look into fixing that up, too. > >-- >Jens Axboe > >-- >To unsubscribe from this list: send the line "unsubscribe fio" in >the body of a message to majordomo@xxxxxxxxxxxxxxx >More majordomo info at http://vger.kernel.org/majordomo-info.html Ah, I just sent an email to you noticing that... :-) Scott Emery emery@xxxxxxx -- To unsubscribe from this list: send the line "unsubscribe fio" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
