On Fri, Jun 10, 2016 at 06:54:24AM -0700, timfelgentreff wrote:
> I added the VM today, and then realized I haven't built in a variation point
> for choosing the image - and I only have a script to build a Spur image
> right now. So I regret that this wasn't (as I first assumed) a thing of 2
> minutes. But I'll get to it.
> 

Let me know if I can help. Attached is a script for building the VM from
latest SVN sources (the install step is commented out).

Choosing the image might be harder. ckformat can be used to select a VM
for an image, but the interpreter VM can only run a V3 image (not Spur),
so maybe the comparison is not so meaningful. I have been maintaining a V3
mirror of Squeak trunk (http://build.squeak.org/job/FollowTrunkOnOldV3Image/)
but I will not be maintaining long term (only a few more months or so).

On balance, maybe it is better to use a Stack interpreter VM as the baseline.
This should be similar enough to the context interpreter VM, and it will
run Spur images, so that may be good as a baseline. It would have been nice
to say that "Cog is X times faster than the original interpreter VM" but
comparing to StackInterpreter may be close enough.

Dave


> 
> marcel.taeumel wrote
> > 
> > David T. Lewis wrote
> >> This really looks very useful, and the graphs and trend lines are nice
> >> for
> >> visualization.
> >> 
> >> Would there be any value in adding an interpreter VM as a baseline to
> >> show
> >> Cog/Spur/RSqueak compared to a non-optimized VM?
> >> 
> >> Dave
> >> 
> >> 
> >>> Hi,
> >>>
> >>> I sent around a note earlier about a benchmarking tool that we're using
> >>> internally to track RSqueak/VM performance on each commit. Every time
> >>> Eliot
> >>> releases a new set of Cog VMs, I also manually trigger the system to run
> >>> benchmarks on Cog. (Once we move the proper VM to Github, I will set it
> >>> up
> >>> so we test each commit on the main development branch and the release
> >>> branch, too, so we will have very detailed breakdowns.) We wanted to
> >>> share
> >>> this setup and the results with the community.
> >>>
> >>> We're collecting results in a Codespeed website (just a frontend to
> >>> present
> >>> the data) which we moved to speed.squeak.org today, and it is also
> >>> linked
> >>> from the squeak.org website (http://squeak.org/codespeed/).
> >>>
> >>> We have some info about the setup on the about page:
> >>> http://speed.squeak.org/about. On the Changes tab, you can see the most
> >>> recent results per platform and environment, with details about the
> >>> machines on the bottom. Note that we calculate all the statistics on the
> >>> workers themselves and only send the time and std dev, so the results'
> >>> min
> >>> and max values you see on the website are bogus.
> >>>
> >>> Finally, the code for the workers also is on Github (
> >>> https://github.com/HPI-SWA-Lab/RSqueak-Benchmarking) and the Benchmarks
> >>> are
> >>> all organized in Squeaksource (
> >>> http://www.hpi.uni-potsdam.de/hirschfeld/squeaksource/BenchmarkRunner.html).
> >>> Right now I've just dumped benchmarks from various sources in there,
> >>> that's
> >>> why you see the same benchmark implemented multiple times in different
> >>> ways, and some micro benchmarks don't make too much sense as they are.
> >>> We're happy to get comments, feedback, or updated versions of the
> >>> benchmarking packages. Updating the benchmarking code is easy, and we
> >>> hope
> >>> this setup proves to be useful enough for the community to warrant
> >>> continuously updating and extending the set of benchmarks.
> >>>
> >>> We are also planning to add more platforms, the setup should make this
> >>> fairly painless, we just need the dedicated machines. We've been testing
> >>> the standard Cog/Spur VM on a Ubuntu machine, and today we added a
> >>> Raspberry Pi 1 that is still churning through the latest Cog and
> >>> RSqueak/VM
> >>> commits. We'd like to add a Mac and a Windows box, and maybe SqueakJS
> >>> and
> >>> other builds of the Squeak VM, too.
> >>>
> >>> Cheers,
> >>> Tim
> >>>
> >>>
> > +1
> > 
> > Best,
> > Marcel
> 
> 
> 
> 
> 
> --
> View this message in context: http://forum.world.st/A-speedcenter-for-Squeak-tp4899946p4900414.html
> Sent from the Squeak - Dev mailing list archive at Nabble.com.
-------------- next part --------------
# Fri Jun 10 20:16:37 EDT 2016 dtl
# Compile an interpreter VM from the most recent sources in squeakvm.org repository

#!/bin/sh

REPO=http://squeakvm.org/svn/squeak/trunk

# Get or update the latest platforms sources and generated VMMaker sources
if test -d platforms
then
  svn update platforms
  svn update src
else
  svn co $REPO/platforms
  svn co $REPO/src
fi

if ! test -d build
then
  mkdir build
fi

cd build
cp ../platforms/unix/cmake/Makefile.example Makefile
make clean; make

# Notes: Installation requires root privileges. Installation may conflict with
# previously installed VMs (e.g. Cog, Spur).

if test $?
then
  echo VM build complete
  echo To install the VM as /usr/local/bin/squeak do \"\$ sudo make install\" in the ./build directory
  # sudo make install
fi