You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Settings used:
Column for IDs -> 'Candidate'
Columns to show during merge -> All
Within a cluster, sort by -> Year
Clustering algorithm -> Edit Distance
Maximum edit distance -> 2
Trying to open page 19 on the browser crashes surf.
My understanding is that Surf is throwing too much data at the browser (the clusters are massive, the ones that load have 100, 200-ish people in them), leading to the 'Aw snap' (Chrome error code 5).
Ideally,
We should be able to set an upper limit on cluster sizes (so at most a cluster can have X people).
The pagination logic should have an upper-bound on rows that it'll throw at the browser for a given page. Some preliminary exploration shows that right now, Surf throws 100 clusters per page, regardless of the sizes of these clusters. By setting an upper-bound on rows per page, the number of clusters per page will vary to conform to that limit.
Credits to @ananay95 for finding this edge case that leads to the crash.
The text was updated successfully, but these errors were encountered:
Dataset used: Test_Tamil_Nadu.csv
To replicate the crash:
Settings used:
Column for IDs -> 'Candidate'
Columns to show during merge -> All
Within a cluster, sort by -> Year
Clustering algorithm -> Edit Distance
Maximum edit distance -> 2
Trying to open page 19 on the browser crashes surf.
My understanding is that Surf is throwing too much data at the browser (the clusters are massive, the ones that load have 100, 200-ish people in them), leading to the 'Aw snap' (Chrome error code 5).
Ideally,
Credits to @ananay95 for finding this edge case that leads to the crash.
The text was updated successfully, but these errors were encountered: