On Fri, Feb 25, 2011 at 1:30 AM, Bogdan Szczurek <thebodzio@xxxxxxxxx> wrote: > And let me throw in another thing. It's been in my head for some time > but now I think it's good to show it to the world. Just in the matter > of shear curiosity: I'd like to see some conceptual work/code/working > example/whatever about automatically configurable grid processing. It > may be more of GEGL project than GIMP one, but I believe still > beneficial in the end. Since 3D rendering engines do that, maybe it > would work nice in 2D world too. Of course a metric and some kind of > benchmark would be needed to decide if sending some part of work over > network to another node is beneficial. Anyway I think it have chances > to make things snappy even on slow machines. I see it as a something > between freakin' fat workstations, thin clients with some heavy “mother > goose” and mighty cluster. It would (hopefully ;)) help to use what is > at hand more optimally. GEGL is designed to be able to split up the rendering requests from the public part of it's API internally and to distribute it among threads/processes/hosts without needing changes to the application using GEGL. At the moment there is only experimental support for using threads in this fashion, but the architecture has been made with distributed processing in mind. This also applies to the GeglBuffers for which there a few years ago already was done experiments with doing multi process/user concurrent manipulation of the same buffers. /Øyvind K. -- «The future is already here. It's just not very evenly distributed» -- William Gibson http://pippin.gimp.org/ ; http://ffii.org/ _______________________________________________ Gimp-developer mailing list Gimp-developer@xxxxxxxxxxxxxxxxxxxxxx https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
