nextcloud / nextcloud/recognize

Parellel GPU and CPU use

Open
#1,223 3 comments 5 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
PHP
Stars
699
Forks
68
Avg merge
1d 4h
Merged PRs (30d)
5

Description

Describe the feature you'd like to request

Recognize to launch preview generation for next batch of GPU based processing at the time of launching GPU processing.

Describe the solution you'd like

CPU used to generate previews whilst GPU processes previews from previous CPU batch.
It would double the speed of processing vs current linear approach of: generate previews (CPU used), once finished, pushed to GPU processing. At the same time, background process could be launched to generate previews required for next run.

Describe alternatives you've considered

Current implementation spends half if not more of the time generating previews using CPU whilst GPU is left unused and vice versa when previews are generated and GPU kicks in, CPU is relatively unused.

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

No files, tests, or entry points are named. Start by tracing the current preview-generation and GPU-processing flow, then determine how batches are handed between CPU and GPU. Done means the next CPU preview batch can run while the GPU processes the previous batch, with throughput validated against the current linear approach.

Written by the indexing model from the issue text.

Assessment

Tech stack
machine-learning, php
Domain
machine-learning, performance
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.