[feature request] neuroglancer http accessor profiler

[xgui3783]

Is there an interest in adding a profile functionality to neuroglancer-scripts? (similar to scale-stats)

Usecase: we would like to be able to

1/ monitor the "liveliness" of a VM serving precomputed volume

2/ simulate average usecases (e.g. 10 concurrent users) and test the performance (average/median/min/max response time) of image services

I would imagine the usage would be something like:

# N.B. not yet implemented
profile-precomputed [-c/--concurrent int=1] \
  [-n int=1] \
  [-t/--threshold_ms int=-1] \
  PRECOMPUTED_URL1 [PRECOMPUTED_URL2] ...

I would imagine for each iteration the script would select a random x, y, z, level, then fetch volumes at +- 3 levels, with appropriate bounding box (bound by the limit of the volume)

We will happy to put in work for this utility, as we foresee that we will need to create such a utility in any case.

The question is, is neuroglancer-script a good/correct place for such utility?

would love to hear your thoughts @ylep

[ylep]

Well, this is a rather specific use-case, so I would not make it a priority, but I'd definitely incorporate the code if you want to contribute it! (as long as it does not add a significant burden, e.g. extra dependencies, to the main neuroglancer-scripts workflows that is data conversion)

[xgui3783]

My naive first impression is that we should not need any more than requests (which is already a dependency) and ThreadPoolExectuor, which is a built in.

But glad to see that there is interest. I will see what I can whip up.