Matches in ESWC 2020 for { <https://metadata.2020.eswc-conferences.org/rdf/submissions/Paper.155_Review.2> ?p ?o. }
Showing items 1 to 10 of
10
with 100 items per page.
- Paper.155_Review.2 type ReviewVersion.
- Paper.155_Review.2 issued "2001-01-16T08:18:00.000Z".
- Paper.155_Review.2 creator Paper.155_Review.2_Reviewer.
- Paper.155_Review.2 hasRating ReviewRating.3.
- Paper.155_Review.2 hasReviewerConfidence ReviewerConfidence.5.
- Paper.155_Review.2 reviews Paper.155.
- Paper.155_Review.2 issuedAt easychair.org.
- Paper.155_Review.2 issuedFor Conference.
- Paper.155_Review.2 releasedBy Conference.
- Paper.155_Review.2 hasContent "The submission follows up on previous work on Web preemption, the concept of allowing a query processor to suspend and resume query execution on order to implement a more fair resource allocation between clients than the first-come-first-server model. The contribution of the current paper is the theoretical foundation and the prototype implementation of an extension that treats aggregate queries (min, max, avg, count, sum), and its comparative empirical evaluation against both the work it extends and against Virtuoso, the state of the art in SPARQL query processing. The paper compares favourably against the former, but not against the latter. This is expected, and should not be considered a failure, as Virtuoso is a production-grade server that implements many optimizations that are outside the scope of this work, and the comparison is always interesting to see. I would recommend that in future work, the authors consider including in their evaluation protocol the simultaneous execution of multiple queries, as the behaviour when allocating resources between multiple clients is their strong point. There will be workloads where their approach outperforms Virtuoso on metrics relevant to fairness, such as "median time to first response between all clients". Editorial: The abstract claims that experimental results demonstrate outperforming existing approaches by "several orders of magnitude" in terms of execution time and the amount of transferred data. This statement raises expectations that are not met in the paper: a factor of 100 is a significant improvement, but I don't recommend promising "several order of magnitude" and delivering 10^2. Minor editorial: Bottom of page 6: "more bigger" Bottom of page 10: "waits for its non-interruptible section to complete and then suspend query execution" -> "... suspends query execution" In reference 24, fix the .bib so that HBase maintains its capitalization."".