mapbox / mapbox/tile-reduce

How CPU utilization is distributed?

Open
#115 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
185
Forks
31
PR merge metrics
No merged PRs in 30d

Description

Is there any documentation on how CPU and memory allocation is done for a tile-reduce script?

A tile-reduce script which is running in a 32 CPU core machines uses all the cores to process 400 tiles uses all the cores initially for 4-5 tiles and then only one CPU is allocated till the end.

What might be the issue here? Is this the issue with cached memory or because of too many operation happening inside map.js?

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the tile-reduce documentation and the map.js operations described in the report. Determine whether CPU and memory allocation for a 32-core, 400-tile run is documented, and identify what evidence is needed to explain the change from many active cores to one. Done means the documented behavior and any confirmed cause answer the reporter's questions.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
data-engineering
Issue type
Documentation
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.