Summary
This paper studies dynamic algorithms for k-median (and k-means) in general metrics. The main result is an \tilde{O}(k) update time, poly(k) query time algorithm that achieves O(1)-approximation. Here, the update model is point insertion/deletion, and the algorithm has access to the distance oracle. A query operation asks to return a list of k points that is O(1)-approximate.
The result improves over the k^2 update time achieved in HK20. This is achieved using a somewhat different but more direct approach. In particular, in HK20, a general reduction to coreset via merge-and-reduce framework was employed, but this work employs a direct dynamization of MP04.
Comprehensive experiments are also provided. Compared with HK20 as a baseline, the new algorithm runs faster and achieves an overall better accuracy.
Strengths
- The paper achieves near-linear in k update time, which is a nice improvement over the previous k^2
- The experiments are convincing, and justify the theoretical improvement
- A nearly-matching lower bound is provided
Weaknesses
- This work only yields O(1)-approx, while HK20 uses coreset approach and hence can build an eps-coreset even for general metrics (even though it does not imply an efficient algorithm for finding a solution). This also means this work cannot be easily generalized to the Euclidean case, where near-linear time PTAS was known.
- The query time is k^2, which may be improved
Questions
- The first paragraph of "our techniques" tried to explain why HK20 has k^2 dependence, but it's not very clear. Here, the black-box coreset is linear in k, and the depth of the binary tree is O(log n). Then how come we have another k factor?
- Followup of the above question: is it true that HK20 relies on a bi-criteria solution? Is that part constitute the bottleneck? Also, does HK20 give bi-criteria solution whose update time is near-linear in k? If so, then maybe it's also an interesting angle to compare with their result, since yours may be viewed as a (strict) improvement of it.
- In the end of Sec 1, it is mentioned that an algorithm for weighted k-median is presented in Sec 2. But I didn't find it
- In Sec 3.1, it seems the algorithm only returns a bi-criteria solution. What's the procedure for making it a real feasible solution? How does that procedure affects the final time complexity?
Rating
6: Weak Accept: Technically solid, moderate-to-high impact paper, with no major concerns with respect to evaluation, resources, reproducibility, ethical considerations.
Confidence
3: You are fairly confident in your assessment. It is possible that you did not understand some parts of the submission or that you are unfamiliar with some pieces of related work. Math/other details were not carefully checked.
Limitations
I didn't find these explicitly discussed. A discussion of limitations, and possibly mentioning future directions, could be helpful. This paper is a theory paper and I don't see a potential negative societal impact.