Effects: update performance wiki page

benchmarks/Makefile

@@ -153,6 +153,11 @@ time-effects.svg: __run_effects
 	 -omit fannkuch_redux \
 	 -omit fannkuch_redux_2 \
 	 -omit loop \
+	 -omit boulderdash \
+	 -omit cubes \
+	 -omit minesweeper \
+	 -omit planet \
+	 -omit ocamlc \
 	 -max 5 -svg 7 400 150 -edgecaption -ylabel "Execution time" \
 	 > $@
 

manual/performances.wiki

@@ -26,12 +26,12 @@ See how various js_of_ocaml options affect the generated size and execution time
 <<a_img src="performances/time-optim.png" | Relative execution times >>
 
 We show the performance impact of supporting effect handlers. The code
-is about 50% larger. The impact on compressed code is actually much lower
+is about 30% larger. The impact on compressed code is actually much lower
 since we are adding a lot of function definitions, which are rather
 verbose in JavaScript but compress well: the compressed code size
-increase by about only 5% for large files compressed with {{{bzip2}}}.
+hardly increases for large files compressed with {{{bzip2}}}.
 Code that involves a lot of function calls without allocation, such as
-{{{fib}}}, becomes much slower. The overhead is more reasonable for
+{{{fib}}}, becomes much slower. The overhead is reasonable for
 code that performs a lot of allocations ({{{hamming}}}) or that
 performs some numeric computations ({{{almabench}}}, {{{fft}}}).
 Exception handling is faster ({{{boyer}}}).