yes, but rizel will give us a good comparison between different versions of our own systems, but now agains others (because rizel=interpreter=old and slow) :) not that it is bad, but I would prefer a dedicated machine.
said so... I think if we have the benchmarks, I think we can annoy Stef enough to get a dedicated benchmark machine... not a terrible new one, but good enough :) but we need to have the benchmarks first, otherwise is loosing time, he. Esteban On May 25, 2013, at 1:47 PM, Camillo Bruni <[email protected]> wrote: > > On 2013-05-25, at 13:46, Igor Stasenko <[email protected]> wrote: > >> On 25 May 2013 13:20, Camillo Bruni <[email protected]> wrote: >>> >>> On 2013-05-25, at 13:14, Esteban Lorenzano <[email protected]> wrote: >>> >>>> >>>> On May 25, 2013, at 1:05 PM, Camillo Bruni <[email protected]> wrote: >>>> >>>>> A couple of them are in Smark >>>>> >>>>> http://smalltalkhub.com/#!/~StefanMarr/SMark >>>>> >>>>> >>>>> On 2013-05-25, at 12:55, Esteban Lorenzano <[email protected]> wrote: >>>>>> I wonder if there are benchmarks around. >>>>>> Also I wonder if there would be useful :) >>>>>> For "marketing" purposes I think yes: if we can put in the web page that >>>>>> we are running those benchmarks, it is cool for "seriousness" (that, of >>>>>> course, assuming the results will not be terribly bad :P) >>>>> >>>>> I know I am a major pain in the ass, but where do you plan to run these >>>>> tests? >>>> >>>> yes, you are ;) >>>> nah, I do not have any idea where to run them... I even doesn't know if I >>>> will, I was just thinking in loud. >>>> but yes, I think it would be good if we can have recurrent (and reliable) >>>> benchmarks to show :) >>> >>> >>> We ran a couple of benchmarks with the FulltextSearch project using the >>> rizel command line handler: >>> https://ci.inria.fr/rmod/job/FullTextSearch/plot/? >>> >>> ./pharo $JOB_NAME.image rizel --packagesMatching='FullTextSearch*' >>> --reporter=RizelXMLReporter >> rizel.xml >>> >>> so basically everything is there :) >> >> yeah.. that what we actually wanted to do since a while.. when we >> first started using CI.. >> Unfortunately for that we need a fully controllable environment: no >> virtualization, sorry.. > > well you can perfectly use Rizel in a virtualized environment > >
