cry for help - make this faster.

[Ara.T.Howard]

yes, it will require deep ruby and 'c' knowledge

http://codeforpeople.com/lib/ruby/acgi/acgi-0.1.0/README

and, obviously

http://codeforpeople.com/lib/ruby/acgi/

i think it's a potentially powerful idea. if you know how to make it faster,
please do so and send in a patch. at this point only a factor of 2x is need
to close the gap on fastcgi. at this point the emphasis is on making it as
fast as possible. scalibility and portability might come next.

good luck.

-a

 

[Hans Fugal]

yes, it will require deep ruby and 'c' knowledge

http://codeforpeople.com/lib/ruby/acgi/acgi-0.1.0/README

and, obviously

http://codeforpeople.com/lib/ruby/acgi/

i think it's a potentially powerful idea. if you know how to make it
faster,
please do so and send in a patch. at this point only a factor of 2x is
need
to close the gap on fastcgi. at this point the emphasis is on making it as
fast as possible. scalibility and portability might come next.

good luck.

-a

That looks way cool. I heartily support it. I have some C IPC
experience, but not in windows.

 

[Jonas Hartmann]

yes, it will require deep ruby and 'c' knowledge

http://codeforpeople.com/lib/ruby/acgi/acgi-0.1.0/README

and, obviously

http://codeforpeople.com/lib/ruby/acgi/

i think it's a potentially powerful idea. if you know how to make it
faster,
please do so and send in a patch. at this point only a factor of 2x is
need
to close the gap on fastcgi. at this point the emphasis is on making it as
fast as possible. scalibility and portability might come next.

good luck.

-a

this is a great thing - could it make it into ruby 2 std lib ( or did
i get something wrong) ?

 

[ara.t.howard]

That looks way cool. I heartily support it. I have some C IPC experience,
but not in windows.

have a whack at it! ;-) i played with threaded versions, non-threaded
versions, versions using mmap, versions using named pipes, versions using
shared memory (sysv ipc), etc. none were significantly fast than the simple
version. also, i was trying to make a *nix impl which at least stood a chance
of being ported to windows - thus the use of named pipes.

at the moment it's just a toy, but it could become something.

regards.

-a

 

[ara.t.howard]

this is a great thing - could it make it into ruby 2 std lib ( or did i get
something wrong) ?

i suppose that's an idea - but at this point it's far from ready for prime
time.

cheers.

-a

 

[M. Edward (Ed) Borasky]

yes, it will require deep ruby and 'c' knowledge

http://codeforpeople.com/lib/ruby/acgi/acgi-0.1.0/README

and, obviously

http://codeforpeople.com/lib/ruby/acgi/

i think it's a potentially powerful idea. if you know how to make it
faster,
please do so and send in a patch. at this point only a factor of 2x is
need
to close the gap on fastcgi. at this point the emphasis is on making it as
fast as possible. scalibility and portability might come next.

good luck.

-a

Hmmm ... by portability do you mean "runs on other than Linux?"

What sort of performance testing framework are you using?

 

[ara.t.howard]

Hmmm ... by portability do you mean "runs on other than Linux?"

i'm afraid so - sigh...

on a side note, i hear 2.6.17 will auto-tune the tcp-ip stack, that ought to
make for a fast web app server...

What sort of performance testing framework are you using?

just ab ;-)

this is still in the proof of concept phase for sure.

cheers.

-a

 

[M. Edward (Ed) Borasky]

i'm afraid so - sigh...

on a side note, i hear 2.6.17 will auto-tune the tcp-ip stack, that
ought to
make for a fast web app server...

I was thinking Tux, actually.

just ab ;-)

There are quite a few out there.