diff options
| author | dearblue <[email protected]> | 2019-05-17 22:04:25 +0900 |
|---|---|---|
| committer | dearblue <[email protected]> | 2019-05-17 22:32:01 +0900 |
| commit | a14ae801022291bfa7ffcc15d1acbc0fea3407a6 (patch) | |
| tree | d63b9ab9591ce83c45e7d89273e408366817dc27 /src | |
| parent | a46da9e44d63c6bfdc591c204bf2704a0dc5b10f (diff) | |
| download | mruby-a14ae801022291bfa7ffcc15d1acbc0fea3407a6.tar.gz mruby-a14ae801022291bfa7ffcc15d1acbc0fea3407a6.zip | |
(Proof of Concept) mruby tuning profiles [ci skip]
Not only mruby, it is one of the difficult things to adjust the performance vs. memory efficiency of the software.
If the approximate target device is divided and the adjustment value for it is prepared by default, it is a good indicator to do fine adjustment.
This PR divides into four profiles.
***Caution: There is no basis for the definitions in the patch.***
- `MRB_CONSTRAINED_BASELINE_PROFILE` - for microprocessors. Reduce memory consumption.
- `MRB_BASELINE_PROFILE` - Default value of mruby.
- `MRB_MAIN_PROFILE` - For desktop computers. Assume that a huge amount of RAM, 10 MiB or more, is on board.
- `MRB_HIGH_PROFILE` - for servers. Assume that mruby VM has a long life.
As you can see the profile name has been ~~stolen~~ imitated from H.264.
Diffstat (limited to 'src')
0 files changed, 0 insertions, 0 deletions