Hmm, I'll try to figure out why the nightly benchy is uploading such degenerate JFR zip files!
Mike McCandless http://blog.mikemccandless.com On Sat, Mar 18, 2023 at 5:16 AM Anton Hägerstrand <an...@blunders.io> wrote: > I've had a look now - it seems like the .jfr.gz files uploaded for these > search benchmarks are empty (they are well formed gzip files, there is just > no compressed data in them). Creation of these .jfr.gz files happens as > part of the benchmark setup, where I don't (to my knowledge) have access to > any logs. > > Mike McCandless is probably the person best suited to dig into this, but > I'm here for any questions and will happily help debug the issue as much as > I can. > > Blunders should also do a better job at saying "no data found" instead of > throwing an error as well. I will look into this. > > Thank you > Anton > > On Fri, 17 Mar 2023 at 20:17, Anton Hägerstrand <an...@blunders.io> wrote: > >> Hi! Anton from Blunders here. >> >> I will take a look as soon as possible, most likely I will be able to >> tell what's going on from server logs. Thank you for reporting - I will put >> up better monitoring in the future. >> >> /Anton >> >> >> On Fri, 17 Mar 2023, 19:49 Marc D'Mello, <marcd2...@gmail.com> wrote: >> >>> Hi all, >>> >>> I was looking at some of the profiles on Blunders (which is linked from >>> the nightly benchmarking site: >>> https://home.apache.org/~mikemccand/lucenebench/) and it seems like >>> some of the latest Searching profiles are not working. For example: >>> https://blunders.io/jfr-demo/searching-2023.03.16.18.02.48/jvm_info. >>> The indexing profiles seem to be working fine as far as I can tell, so I >>> wonder if this is a problem with how the nightly benchmarks are >>> publishing data to the Blunders API. >>> >>> Thanks, >>> Marc >>> >>
