Hi Richard, > > It would be great if we could just do a PR with your changes, but the > commit messages are supposed to have a specific format including a > Jira issue number. So at least the commit messages would need to be > rewritten or the PR would need to be squash-merged. The format of the > commit messages should look as follows: > > ``` > [UIMA-6291] Improve uimaFIT benchmarking module > > - Remove unused dependency > - ... other changes > - ... other changes
I managed finally to clean up the messages after all, although my IDE send me on a detour at first, which almost prompted me to give up. However, it should follow the guide lines now. > > That might be because the CASes are only generated to by max 130 offset > positions long leading to a quite high density of annotations > and thus t-coveredBy-s may not be able to profit too much from its abiltiy to > seek fast and to abort early. Probably the benchmark > shoud be adjusted to expand the offset space as more annotations get added > for a lower annotation density. > > ... or there is some measurement/calculation bug … It Is indeed strange that there shouldn’t be a larger difference. I am running it from my branch, which is based on an older version of the benchmarks, but with user time, and I have a factor 11 in difference, which is more like what I would expect. BTW Did you see my selectAt bug report? https://issues.apache.org/jira/browse/UIMA-6294 Cheers Mario ________________________________ Disclaimer: This email and any files transmitted with it are confidential and directed solely for the use of the intended addressee or addressees and may contain information that is legally privileged, confidential, and exempt from disclosure. If you have received this email in error, please notify the sender by telephone, fax, or return email and immediately delete this email and any files transmitted along with it. Unintended recipients are not authorized to disclose, disseminate, distribute, copy or take any action in reliance on information contained in this email and/or any files attached thereto, in any manner other than to notify the sender; any unauthorized use is subject to legal prosecution.
