Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Performance #25

Open
FireCulex opened this issue Aug 30, 2021 · 2 comments
Open

Performance #25

FireCulex opened this issue Aug 30, 2021 · 2 comments
Labels
enhancement New feature or request

Comments

@FireCulex
Copy link

FireCulex commented Aug 30, 2021

vmware_23Sp1ivgSF

Between analyzing frames and stats output it appears only a single core is being utilized the entire time.

real	2m35.610s
user	2m31.817s
sys	0m3.896s

just to analyze a 10 second video.

@stg7 stg7 added the enhancement New feature or request label Nov 30, 2021
@stg7
Copy link
Member

stg7 commented Nov 30, 2021

Yes, sorry for this, the reference implementation is not optimized for speed, and the bitstream parser may create quite long reports (that are even compressed and include far more features that are required for the model itself).

To speed up the calculation it would require developing a reduced video parser, we may check this in the future.

Best
Steve

@stg7 stg7 mentioned this issue Nov 30, 2021
@stg7
Copy link
Member

stg7 commented Nov 30, 2021

also checkout LDJSON report generation

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants