* Mike Gerdts <[EMAIL PROTECTED]> [2008-04-10 12:40]:
> On Thu, Apr 10, 2008 at 3:25 AM, Dan Price <[EMAIL PROTECTED]> wrote:
> >  # ptime pkg image-update  (Null update)
> >  real       15.082
> >  user       12.764
> >  sys         0.229
> >
> >  Just over 6 minutes, or about 4.5MB/s = 36Mb throughput-- not too
> >  shabby.  And clearly, there's room to squeeze that down further,
> >  although some of the optimizations will likely become more challenging.
> >
> >  Anyway, this gives an approximate idea of how fast we might be able to
> >  provision enterprise systems in the data center, in the near future.
> >  Indeed, it could be even faster in a datacenter with gigabit links.
> 
> >From looking at why it was taking so long to build a repository on my
> Ultra 2, I could see that it was spending 90+% of its time in
> compression routines (DTraceToolikt hotuser).  When packages are
> installed the files are decompressed at the client side, right?  If
> they are decompressed on the server side, the same issues will apply
> for CMT repository servers.

  The server side of installation does not do any compression.  The
  server of publication does do compression.  I think one of the next
  RFEs on the publication side is conditional sending, so that so you
  needn't send (and compress) a file that the server already has.

> On a Niagara 2 box, created a /tmp/sbin.tar.gz of /usr/sbin, then used
> "gzcat sbin.tar.gz> /dev/null" and found it could could decompress
> this data at 5.9 MB/s. This would mean that on your 1990's LAN you are
> pushing 76% of the data that one thread of a current system can
> handle.
> 
> Has any thought gone into making pkg multi-threaded?

  Some.  The server is already threaded, although I think we're going to
  move to a WSGI model and start investigating deployment with
  mod_python.  On the client side--and I know this may sound strange--I
  see the low-level potential for threading as tied up with the
  transport issues that I mentioned in the SSL review thread.   However,
  we may be able to do something cruder, sooner, higher up in the
  package or image plan's execute*() routines.

  - Stephen

-- 
[EMAIL PROTECTED]  http://blogs.sun.com/sch/
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss

Reply via email to