Make GForce kick-in smarter

Open
#5,487 2 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
r
Domain
performance

Research direction

No files or tests are named. Start by identifying the GForce entry points and comparing GForce functions with their base equivalents across different .NGRP values; define how small-group behavior and multithreading should be evaluated, then verify the chosen behavior with performance measurements.

Written by the indexing model from the issue text.

Description

GForce performance

A lot of GForce functions only show a speedup when the number of groups in BY is high enough and are even slower than their base equivalents when applied to a small number of groups.

I would like to discuss whether it makes sense to turn off GForce optimization for smaller values of .NGRP

I know that for a single execution of these statements a difference won't be noticeable but it still seems wrong to power up multithreading for no gain at all.

Dominant language
R
Stars
3.9k
Forks
1.1k
Avg merge
14h 4m
Merged PRs (30d)
4

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.

More from Rdatatable/data.table

All issues in Rdatatable/data.table

Similar issues

More R issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.