HI @dan_nm ,
This might actually be a Windows + go problem as explained in this comment the gist of which is that windows time is in general not a very high resolution or at least not as high resolution as it is used by go.
I don’t think we can do much really and the workarounds are:
- introduce a tag to make certain you are not sending metrics with same time and tag set (what you’ve done)
- aggregating metrics in k6 so that this basically isn’t a problem - we plan on doing this but unlikely to happen soon (1-2 releases)
- Try telegraf for aggregating metrics … .although my experience is spotty. So far the best I have managed to do is
statsd
input (which aggregates quite well) + influxdb output (in my case influxdbv2, but that really isn’t necessary AFAIK). Here is influxdbv1->influxdbv2 setup with some aggregation that isn’t great (as noted in the comment). - I wonder if influxdbv2 hasn’t fixed it and trying GitHub - li-zhixin/xk6-influxdbv2: A k6 extension output to influxdb. would help
- Don’t use windows for running your load tests