Comments (9)
I think the first step is to add :nruns 1
to the value returned by esup-profile-sexp
, and then implement a esup-merge-results
function that takes a list of results for the same sexp and merges them into averages (and standard deviations?).
from esup.
I'll brush up on my stats and look into implementations. I think we'd get better results by just running Esup n times, but having the Emacs Frame appear multiple times would get old.
Looking into the issue, I don't think we can just re-benchmark sexps in the same emacs. It won't work for code that only executes once, like require
. As an example, eval the following code:
(loop for i from 1 to 5
collect (benchmark-run (require 'ruby-mode)) into results
finally return results)
;; This returns the below on my machine:
((0.007 0 0.0) (0.0 0 0.0) (0.0 0 0.0) (0.0 0 0.0) (0.0 0 0.0))
Only the first iteration takes any time.
from esup.
The default should probably be to run just once, but for people that want better statistics, running multiple times could be an option.
But honestly, this probably isn't a high-priority thing.
from esup.
By the way, another consideration is that some people auto-compile their init files, so it would make sense to have an option to run the init once and throw away the results and then do the real run, to get the results for an already-compiled init.
from esup.
So, are you suggesting that we compare the byte-compiled vs interpreted
version? There's emacs-init-time which shows the total init time. But
emacs-init-time includes everything for Emacs. Esup time + Emacs -q time
are usually way less than emacs-init-time and I'm not totally sure why.
I'll take a peek at the internals and see if I can figure something out.
On Mon, Aug 18, 2014 at 7:46 PM, Ryan C. Thompson [email protected]
wrote:
By the way, another consideration is that some people auto-compile their
init files, so it would make sense to have an option to run the init once
and throw away the results and then do the real run, to get the results for
an already-compiled init.β
Reply to this email directly or view it on GitHub
#4 (comment).
from esup.
No, I'm just suggesting that it would be useful to be able to run the init process once and throw away the result, and then run it for real a second time and keep the results.
from esup.
Okay, I'll take a look next week.
On Mon, Aug 25, 2014 at 6:43 PM, Ryan C. Thompson [email protected]
wrote:
No, I'm just suggesting that it would be useful to be able to run the init
process once and throw away the result, and then run it for real a second
time and keep the results.β
Reply to this email directly or view it on GitHub
#4 (comment).
from esup.
So, my week estimate was waaaay off.
I don't think I can implement this without rewriting significant parts of the code and I'm not sure that the added complexity would justify getting an average.
I'm gonna close it, but if there's significant interest I'll take another look.
from esup.
Yeah, that's pretty much the conclusion I came to after looking at it. No problem.
from esup.
Related Issues (20)
- Error on Emacs 26.1 HOT 27
- Esup breaks on 25.3 flymake
- Emacs 26.1 + macos, suspicious profile HOT 2
- esup can't parse profiled result contains package comment-tags
- βSymbolic link to Git-controlled source file; follow link? (yes or no) β HOT 4
- esup is incompatible with package.el HOT 1
- esup chokes on empty config files
- [Bug] - No indentation in *esup* buffer. HOT 9
- Use other mode instead of `fundamental-mode`.
- How to use?
- Byte compile warnings HOT 1
- Migrate to GitHub Actions HOT 2
- Release stavle v0.7 HOT 1
- Refactor tests to use buttercup HOT 4
- Cannot open load file: No such a file or directory, s HOT 6
- Emacs 27.1 unnecessary (package-initialize) error HOT 2
- (wrong-type-argument (or eieio-object class) nil obj) in Emacs 28 HOT 16
- Segmentation fault. HOT 1
- esup mistaking ;;; file ends here, as variable, void variable "here" HOT 3
- early-init.el is not included in profiling
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
π Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. πππ
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google β€οΈ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from esup.