Skip to content
This repository was archived by the owner on Apr 5, 2024. It is now read-only.

Poor performance on large projects #14

Closed
GoogleCodeExporter opened this issue Jul 15, 2015 · 7 comments
Closed

Poor performance on large projects #14

GoogleCodeExporter opened this issue Jul 15, 2015 · 7 comments
Labels
auto-migrated Milestone-0.9.6 Priority-Medium Type-Defect

Comments

@GoogleCodeExporter
Copy link 

1. Run cppcheck on a large project

It just takes too much time. With such performances, I'd rather launch it
on a server.

It seems that a new cppcheck process is forked for each source code, so
that there is a big overhead.

And it would be nice to be able to perform a remote launch, or at least to
be able to give a result file as input.

Original issue reported on code.google.com by mathieu....@gmail.com on 5 May 2010 at 9:00
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
auto-migrated Milestone-0.9.6 Priority-Medium Type-Defect
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@GoogleCodeExporter