From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-0.9 required=5.0 tests=BAYES_00,FORGED_GMAIL_RCVD, FREEMAIL_FROM autolearn=no autolearn_force=no version=3.4.4 X-Google-Thread: 103376,68494635acddb77e X-Google-Attributes: gid103376,domainid0,public,usenet X-Google-Language: ENGLISH,ASCII-7-bit Path: g2news2.google.com!postnews.google.com!e39g2000hsf.googlegroups.com!not-for-mail From: Maciej Sobczak Newsgroups: comp.lang.ada Subject: Re: File output and buffering Date: Thu, 21 Aug 2008 13:54:25 -0700 (PDT) Organization: http://groups.google.com Message-ID: <4db7770e-a53b-436b-bc87-b487fdec430b@e39g2000hsf.googlegroups.com> References: <60a35fd4-e5a6-4aa0-a73f-6815ce7e92fc@f36g2000hsa.googlegroups.com> <4af2f934-7458-4370-b325-c38e3a4068b8@s50g2000hsb.googlegroups.com> <1jt8nguvzf1hw$.189glcey6hmht.dlg@40tude.net> <84805bfc-26f4-4507-9024-9e3558c9cb32@m73g2000hsh.googlegroups.com> <104g44sstk0to$.1lektfatijska$.dlg@40tude.net> NNTP-Posting-Host: 85.3.252.233 Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Trace: posting.google.com 1219352065 22163 127.0.0.1 (21 Aug 2008 20:54:25 GMT) X-Complaints-To: groups-abuse@google.com NNTP-Posting-Date: Thu, 21 Aug 2008 20:54:25 +0000 (UTC) Complaints-To: groups-abuse@google.com Injection-Info: e39g2000hsf.googlegroups.com; posting-host=85.3.252.233; posting-account=bMuEOQoAAACUUr_ghL3RBIi5neBZ5w_S User-Agent: G2/1.0 X-HTTP-UserAgent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.0.1) Gecko/2008070206 Firefox/3.0.1,gzip(gfe),gzip(gfe) Xref: g2news2.google.com comp.lang.ada:7467 Date: 2008-08-21T13:54:25-07:00 List-Id: On 21 Sie, 11:24, "Dmitry A. Kazakov" wrote: > > I do not know what is "conveyered". > > Pipelined processing. When you refer to throughput, then it is increased > only because of existence of hidden conveyers, which ultimately always > boils down to some asynchronously working elements. No, there is no asynchronous processing there (usually). There is grouping that leads to smaller number of still synchronous operations. > Well, here we need to clarify what is the I/O end point. No, we do not need to, especially when it is already clear that we would spiral down in an endless philosophy discussion about definitions. It is enough to get a clock and measure two simple test programs. I can offer the test programs if needed. > Ada.Text_IO is slow because of the buffering it does in order to implement > a protocol (pages) which you do not need. I do not see how paging could be related here. Or at least I can imagine an implementation where the overhead of bookkeeping pages is less than 15-20x. -- Maciej Sobczak * www.msobczak.com * www.inspirel.com Database Access Library for Ada: www.inspirel.com/soci-ada