Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
F
FFmpeg
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Container Registry
Model registry
Operate
Environments
Monitor
Incidents
Service Desk
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
libremedia
Tethys
FFmpeg
Commits
ac59e7f4
Commit
ac59e7f4
authored
17 years ago
by
Mike Melanson
Browse files
Options
Downloads
Patches
Plain Diff
Ministry of English Composition edits
Originally committed as revision 11597 to
svn://svn.ffmpeg.org/ffmpeg/trunk
parent
5e123bd3
No related branches found
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
doc/optimization.txt
+11
-10
11 additions, 10 deletions
doc/optimization.txt
with
11 additions
and
10 deletions
doc/optimization.txt
+
11
−
10
View file @
ac59e7f4
...
...
@@ -28,16 +28,17 @@ NOTE: If you still don't understand some function, ask at our mailing list!!!
(http://lists.mplayerhq.hu/mailman/listinfo/ffmpeg-devel)
What speedup justifies an optimizetion?
---------------------------------------
Normaly with clean&simple optimizations and widely used codecs a overall
speedup of the affected codec of 0.1% is enough. These speedups accumulate
and can make a big difference after a while ...
Also if none of the following gets worse and at least one gets better then an
optimization is always a good idea even if the overall gain is less than 0.1%
(speed, binary code size, source size, source readability)
For obscure codecs noone uses, the goal is more toward keeping the code clean
small and readable than to make it 1% faster.
When is an optimization justified?
----------------------------------
Normally, clean & simple optimizations on widely used codecs can achieve
an overall speedup of 0.1%. These speedups accumulate and can make a big
difference after awhile. Also, if none of the following factors get
worse due to an optimization -- speed, binary code size, source size,
source readability -- and at least one factor improves, then an
optimization is always a good idea even if the overall gain is less than
0.1%. For obscure codecs that are not often used, the goal is more
toward keeping the code clean, small, and readable than to make it 1%
faster.
WTF is that function good for ....:
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment