disk, 1TB. why it matters ? from my profile its clear that its not the primitive that is the problem but how Pharo processes pngs.

I happen to work with a lot of big data both in 3d graphics, a blender file can easily reach 250 mb and it opens under a second and audio files , plus instrument that uses alot of audio files as samples of several gbs giving again instanenous loading. I am not talking here 60 files, I am talking thousands of files.

I report a sever limitation and I have been told

a) I have not done enough to isolate the problem when I post clear profiling reports and the code that is responsible for it

b) why I make a fuss about it since there are work arounds

c) that its a hardware limitation when the hardware is able to perform light years ahead of what pharo is currently doing

Sorry but this kind of attitude is really bad, when someone reports a bug I find it a lot better to tell him that you don't care or not reply at all and ignore him than just find excuses for the bug or limitation.

I see it every single time I complain about a problem there is a few people who are logical about this like Ben , Esteban etc and then some other that in complete denial zone and easily offended by the truth.

On Sat, Jan 16, 2016 at 4:07 PM Stephan Eggermont <[hidden email]> wrote:

On 16-01-16 14:48, Dimitris Chloupis wrote:
> sorry but thats plain horrible performance wise and those images are
> needed as soon as the gui is opened. So there can be no lazy loading for
> them. The total size for all the 60 images is 530kbs . What would happen
> if I did some serious animations of 10s of mbs , I will have to go to
> buy a coffee to get my GUI opened :D

Is that on a disk or an SSD? You won't be able to get much more than 60
files opened/s on a disk.

Stephan