On May 7, 1:19 pm, mhampton <[EMAIL PROTECTED]> wrote:
> I wonder what version the "30 seconds" comment was from. The code
> base is probably growing faster than processor/hard drive speeds.
>
> On my Macbook, 2.4 Ghz intel chip, 5400rpm drive, a first clone of 3.0
> takes about 1 minute, the second clone 30 seconds.
This is from a brand-new, just downloaded, binary build?
>
> -M. Hampton
>
> On May 7, 1:15 pm, John H Palmieri <[EMAIL PROTECTED]> wrote:
>
> > On May 7, 11:35 am, "William Stein" <[EMAIL PROTECTED]> wrote:
>
> > > On Wed, May 7, 2008 at 11:27 AM, Nick Alexander <[EMAIL PROTECTED]> wrote:
>
> > > > On 7-May-08, at 11:14 AM, John H Palmieri wrote:
>
> > > > > In Section 7.1 of the Sage Programming Guide, it says
>
> > > > >> Creating clones of a repository should be fairly fast, e.g., about
> > > > >> 30 seconds.
>
> > > > > I just installed a fresh copy of Sage on my Mac and ran 'sage -clone
> > > > > blah', and it took almost 15 minutes to complete. Running 'sage
> > > > -clone
> > > > > temp' a second time took just over one minute. Neither of these, and
> > > > > especially not the first one, is "about 30 seconds".
>
> > > > Cloning a repository is limited by your disk's throughput and
> > > > latency. Your second run is working with a primed disk cache -- this
> > > > says a lot about your disk's random access :)
>
> > > > > This is on a 2.4 GHz Mac Book Pro.
>
> > > > I have a similar machine and cloning is reasonably snappy. I had an
> > > > older Powerbook and the disk was ridiculously slow.
>
> > > > You might find mercurial queues lets you work with fewer clones.
>
> > > > Nick
>
> > > I think the main point of John's email is that we should update the Sage
> > > Programming guide with the remarks you make above.
>
> > > Is that right John?
>
> > Yes, that's right.
>
> > > 15 minutes for a first clone is very very very weird though. It's just
> > > copying a bunch of files. Maybe something else was going on with
> > > your computer, e.g., os x was building some spotlight index or
> > > something...
>
> > I'm doing this starting from a binary build, so according to didier's
> > post, there is some extra work that's going on. Certainly according
> > to the messages that sage prints out during the cloning, it's
> > compiling a bunch of files, not just copying things.
>
> > > William
--~--~---------~--~----~------------~-------~--~----~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~----------~----~----~----~------~----~------~--~---
