Why is my data taking so long to load?

Initial Dataset Load

The first time a dataset opens, CartoScope fetches the catalog.yaml metadata and any tile indexes. This is a one-time cost per session.

• External datasets (AWS S3, Zenodo) may be slower depending on network latency and server location.
• Check your internet connection speed if delays are consistently long.

Layer Rendering

• Many active layers: Each visible layer renders independently. Hide layers you are not currently using via the visibility toggle in the Layer Drawer.
• Factor pixel layers (RAW_PIXEL) are more GPU-intensive than raster layers. If rendering feels slow, switch to a raster or hex layer when a pixel-level view is not needed.
• Gene layers with many genes (gene group layers) require more computation. Consider splitting very large gene groups.

ROI Data Loading

Large ROIs with "Full ROI Loading" enabled fetch all raw pixel data at maximum resolution, which can be slow and memory-intensive.

• Use Current-Level Loading instead for large ROIs or during exploration.
• See ROI Loading Data Options for a full comparison.

Browser & Hardware

• Hardware acceleration: Ensure GPU acceleration is enabled in your browser settings (Chrome: chrome://settings/system → "Use graphics acceleration when available").
• Available RAM: Close unused tabs if the browser is competing for memory with a large dataset.