Re: [Pharo-dev] FileTree/Iceberg and SSDs, change the file format

2017-05-24 Thread Jan Vrany
On Wed, 2017-05-24 at 11:46 +0530, K K Subbu wrote: > On Tuesday 23 May 2017 08:37 PM, Jan Vrany wrote: > > Hi, > > > > > > Is it possible to build a file responder right into Pharo and > > > > expose packages through WebDAV or FUSE or sshfs service? Then > > > > the > > > > contents can go

Re: [Pharo-dev] FileTree/Iceberg and SSDs, change the file format

2017-05-23 Thread Jan Vrany
Hi, > > Is it possible to build a file responder right into Pharo and > > expose packages through WebDAV or FUSE or sshfs service? Then the > > contents can go directly from RAM (pharo) to RAM (repo server or > > git) without going through slow disk filesystem. > > Yes it's possible and really

Re: [Pharo-dev] FileTree/Iceberg and SSDs, change the file format

2017-05-23 Thread Dale Henrichs
Stephan, Out of curiosity. Why are you copying the git repo? In my normal usage, I clone a git repository on disk and then share that repository amongst all of the image/stones on that machine ... The upshot is that I almost never copy the repo. I use push to publish changes to common git

Re: [Pharo-dev] FileTree/Iceberg and SSDs, change the file format

2017-05-23 Thread Ben Coman
On Tue, May 23, 2017 at 1:33 PM, Stephan Eggermont wrote: > On 22/05/17 04:38, Ben Coman wrote: > >> On Sun, May 21, 2017 at 11:25 PM, Stephan Eggermont >> > > wrote: >> So this was copying files at the OS level? Which OS? >> > >

Re: [Pharo-dev] FileTree/Iceberg and SSDs, change the file format

2017-05-22 Thread K K Subbu
On Sunday 21 May 2017 11:34 PM, Dale Henrichs wrote: As part of his work on Cypress 2.0 Martin McClure is planning on supporting a file per class disk format in addition to the file per method format and possibly a file per package format. I'm not sure whether Martin is at the point where he is

Re: [Pharo-dev] FileTree/Iceberg and SSDs, change the file format

2017-05-21 Thread Ben Coman
On Sun, May 21, 2017 at 11:25 PM, Stephan Eggermont wrote: > At the PharoDays I was painfully reminded that SSDs perform really badly > when using small files. The Bloc tutorial used a github filetree repo and > that has a lot of files. The whole folder is 116 MB in 16K files.

Re: [Pharo-dev] FileTree/Iceberg and SSDs, change the file format

2017-05-21 Thread Thierry Goubier
Le 21/05/2017 à 17:25, Stephan Eggermont a écrit : At the PharoDays I was painfully reminded that SSDs perform really badly when using small files. The Bloc tutorial used a github filetree repo and that has a lot of files. The whole folder is 116 MB in 16K files. Copying that amount of data

Re: [Pharo-dev] FileTree/Iceberg and SSDs, change the file format

2017-05-21 Thread Dale Henrichs
Cuis uses a standard chunk file format[1] with a file per package. Given the fact that no two Smalltalk dialects share a common class creation protocol makes simply using chunk file format a non-starter. Squeak uses FileTree. As part of his work on Cypress 2.0 Martin McClure is planning on

Re: [Pharo-dev] FileTree/Iceberg and SSDs, change the file format

2017-05-21 Thread philippe.b...@highoctane.be
There is the same kind of issues with Hadoop but the block size is 128MB. So, lots of small files give the same issue. This is solved by having HAR files (Hadoop Archive) that contain the files. The haddop filesystem is usually able to access the har contents somewhat transparently from

[Pharo-dev] FileTree/Iceberg and SSDs, change the file format

2017-05-21 Thread Stephan Eggermont
At the PharoDays I was painfully reminded that SSDs perform really badly when using small files. The Bloc tutorial used a github filetree repo and that has a lot of files. The whole folder is 116 MB in 16K files. Copying that amount of data should not be noticable, taking about a third of a