I am noticing some interesting differences in the Neo4J browser depending on the browser used. The graph in the backend is rather large several million nodes and over 50 million edges. So some queries tend to be rather large, especially if it's of the type where one aggregates a large number of results.
On Safari 13.1.1 given a demanding query, the browser starts eating up ram up to several gigs then Safari kills the tab due to memory constraints (AFAIK the threshold is not tunable). The same query on the same graph, via Chrome, is heavy on the CPU instead. It maxes out all cores while not creating a significant memory footprint (at least not on the same scale as Safari).
Is this intentional? What could that be due to? Are there any documents one can read about differential performance based on the browser?
Thanks in advance