Return-Path: Delivered-To: apmail-cocoon-dev-archive@www.apache.org Received: (qmail 91815 invoked from network); 9 Jun 2004 21:14:16 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 9 Jun 2004 21:14:16 -0000 Received: (qmail 83385 invoked by uid 500); 9 Jun 2004 21:14:27 -0000 Delivered-To: apmail-cocoon-dev-archive@cocoon.apache.org Received: (qmail 83343 invoked by uid 500); 9 Jun 2004 21:14:26 -0000 Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: dev@cocoon.apache.org Delivered-To: mailing list dev@cocoon.apache.org Received: (qmail 83237 invoked by uid 99); 9 Jun 2004 21:14:25 -0000 Received: from [66.51.199.81] (HELO mail5.dslextreme.com) (66.51.199.81) by apache.org (qpsmtpd/0.27.1) with SMTP; Wed, 09 Jun 2004 14:14:25 -0700 Received: (qmail 16979 invoked from network); 9 Jun 2004 21:14:00 -0000 Received: from unknown (HELO www.dslextreme.com) (66.51.199.92) by 192.168.8.93 with SMTP; Wed, 09 Jun 2004 21:14:00 +0000 Message-ID: <0a0a0a0a.20040609141400.enycu.tbref@www.dslextreme.com> In-Reply-To: References: <40C73A6F.4030305@reverycodes.com> <40C75BF7.3020703@umn.edu> Date: Wed, 9 Jun 2004 14:14:00 -0700 (PDT) Subject: Re: >*Cough*< Download Size >*Cough*< From: "Ralph Goers" To: dev@cocoon.apache.org User-Agent: DSL Extreme Webmail (www.dslextreme.com) MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 Importance: Normal X-AntiVirus: scanned for viruses by AMaViS 0.2.1 (http://amavis.org/) X-Virus-Checked: Checked X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N Just for grins I ran a du on Cocoon-2.1.5. These numbers don't necessarily correspond to what is in the zip/gzipped tar as source should compress better than jars, but this is what I got. To summarize, out of 95MB 75MB is source and 61MB is in blocks. About 10% (9MB) is scratchpad. The lib directory takes up abuot 12MB. I'd expect that to be pretty much the same inside the zip/gzipped tar, so the vast majority of the rest is probably the compressed source. One way to reduce the size of the download is to remove the dependent jars. This has been discussed here many, many times. However, I'm wondering how much scratchpad stuff should disappear. I haven't looked at what is in it, but shouldn't there be some rule about how long something can stay there? For the root directory I got: 8 blocks.properties 4 build.bat 8 build.properties 4 build.sh 4 build.xml 16 cli.xconf 8 cocoon.bat 8 cocoon.sh 4 CREDITS.txt 4 DESKTOP.INI 8 forrest.properties 40 gump.xml 8 INSTALL.txt 12 KEYS 804 legal 12752 lib 4 README.txt 75652 src 112 status.xml 3500 tools I then ran it again on the src subdirectory: 61768 blocks 16 confpatch 532 deprecated 4916 documentation 4884 java 20 mocks 112 resources 100 samples 520 test 2780 webapp Finally, I ran it against blocks: 188 apples 176 asciiart 328 authentication-fw 1720 axis 2788 batik 900 bsf 824 chaperon 492 cron 1056 databases 7040 deli 156 eventcache 1568 fop 3708 forms 360 hsqldb 260 html 860 itext 376 javaflow 212 jfor 172 jms 180 jsp 176 linkrewriter 884 linotype 552 lucene 948 mail 472 midi 156 naming 1832 ojb 56 paranoid 1024 petstore 56 php 1504 poi 2920 portal 896 portal-fw 200 profiler 268 proxy 148 python 236 qdox 360 repository 9804 scratchpad 5364 serializers 376 session-fw 1508 slide 448 slop 320 stx 192 swf 320 taglib 384 tour 460 velocity 212 web3 992 webdav 3512 woody 708 xmldb 1112 xsp Berin Loritsch said: > Tony Collen wrote: > >> Steven Noels wrote: >> >>> On 09 Jun 2004, at 18:27, Vadim Gritsenko wrote: >>> >>>> Berin Loritsch wrote: >>>> >>>>> Is there any reason the Cocoon source distribution has to be about >>>>> the >>>>> same size download as a current JVM? >>>> >>>> >>>> >>>> >>>> Don't worry, we already discussed this matter with Carsten [1] and >>>> decided that next version of Cocoon will come with bundled JDK. >>> >>> >>> >>> We'll add jar'ed sources of the JDK with that as well, don't we? >> >> >> We might as well include some operating system source while we're at it >> :D > > Which one? You'll have to include source code for Linux, *BSD, MacOSX, > Windows, etc.--you know just to make sure the sockets are working > properly. > > Of course by this time the download will be in the GB region and > will completely be impractical to all who might want to use it.