On Wed, Oct 14, 2009 at 11:17 PM, Adrian Chadd <adr...@squid-cache.org> wrote: > 2009/10/14 Amos Jeffries <squ...@treenet.co.nz>: > > [snip] > > I still find it very amusing that noone else has sat down and talked > about the last 20 + years of writing threaded, concurrent code and > what the pro/cons of them would be here; nor what other projects are > doing. > > Please don't sit down and talk about how to shoehorn SMP into some > existing Squid-3 "thing" (be it AsyncCalls, or anything really) before > doing this. You'll just be re-inventing the same mistakes made in the > past and it will make the project look bad. > > > > Adrian >
Its not like we want to make project bad. Squid was not deployed on smp before because we did not have shared memory architectures (multi-cores), also the library support for multi-threading was like nightmare for people. Now things are changed, it is very easy to manage threads, people have multi-core machines at their desktops, and as hardware is available now or later somebody has to try and build SMP support. think about future....... To cop with internet speed & increase in number of users, Squid must use multi-core architecture and distribute its work............ -- Mr. S. H. Malave Computer Science & Engineering Department, Walchand College of Engineering,Sangli. sachinmal...@wce.org.in
