Re: [Gems-users] Commercial workloads listed in GEMS doc


Date: Fri, 5 Oct 2007 13:04:09 -0500
From: "Lei Yang" <lya755@xxxxxxxxxxxxxxxxxxxx>
Subject: Re: [Gems-users] Commercial workloads listed in GEMS doc
Thank you!

Any idea when GEMS 2.0 will be released?

Thanks,
Lei


On 10/5/07, Derek Hower <drh5@xxxxxxxxxxx> wrote:
> The upcoming GEMS 2.0 release will have support for creating these
> benchmarks.  The initial release (due out soon) will only contain
> support for building OS checkpoints without the workloads running.
> (basically a bare system with Solaris installed, checkpointed
> immediately after login)  You can use these checkpoints as a base to
> start your own benchmark programs.
>
> Additional support for building the apache, jbb, and zeus checkpoints
> will be distributed as a patch shortly after the initial GEMS 2.0
> release.  Support for oltp is pending, although a release should not be
> expected soon.
>
> -Derek
>
> Lei Yang wrote:
> > Dear list,
> >
> > I found in GEMS doc wiki, the gen-script page, that there are four
> > commercial benchmarks listed, namely jbb, oltp, apache, zeus. However,
> > it is indicated that "These files do not exist in the release because
> > we cannot distribute workloads due to licensing issues." I wonder how
> > may one gain access to these benchmarks? From whom shall we get the
> > license?
> >
> > Appreciate your comments!
> >
> > Lei
> > _______________________________________________
> > Gems-users mailing list
> > Gems-users@xxxxxxxxxxx
> > https://lists.cs.wisc.edu/mailman/listinfo/gems-users
> > Use Google to search the GEMS Users mailing list by adding "site:https://lists.cs.wisc.edu/archive/gems-users/"; to your search.
>
> _______________________________________________
> Gems-users mailing list
> Gems-users@xxxxxxxxxxx
> https://lists.cs.wisc.edu/mailman/listinfo/gems-users
> Use Google to search the GEMS Users mailing list by adding "site:https://lists.cs.wisc.edu/archive/gems-users/"; to your search.
>
>
[← Prev in Thread] Current Thread [Next in Thread→]