Server

I recently wrote a simple auth server in Common Lisp which basically uses `select' then parses all incoming connections.

It's single threaded, how well will it hold up against say 1000 people, etc?

It's single threaded
use http://common-lisp.net/project/bordeaux-threads/

>>1
how well will it hold up against say 1000 people, etc?
About 1/2 or 1/3 of the GCC speed, depending on your code.

>>3
you mean two or three times GCC speed?

>>2
Well i know about bordeaux-threads, however, what i should be asking is what's a better solution to my networking?

Currently as i said, i'm one thread for both getting connections and then parsing their data sent (TCP btw)

I hear that 1 thread per connection doesn't scale well once you get a lot of users.

Would it be better to have a separate IO thread (or 2 for writing and reading) and a parsing thread?

You could use:
1. One thread for accepting new connections and placing them on a connection/request queue.
2. One thread to pop connections from the above queue and assign them to worker threads, if available
3. N worker threads that process data and when I/O or CGI scripting is needed they end their work and put the request again in the same request pile, this time with status information that specifies where work stopped before.

IOCP is a good model, you can check it out here:
http://msdn.microsoft.com/en-us/library/windows/desktop/aa365198%28v=vs.85%29.aspx
Though your implementations won't be as efficient as the M$ IOCP one for some kernel optimizations, Linux is lacking on this area...
And for CGI you may want to check out the FastCGI solution.

authism

>>6
That's not the best paradigm, it has cache locality issues.

>>8
This makes me wonder why are asynchronous callbacks so used. To me they just scream like bad design.
Interrupt handlers should be as small as possible for cache locality reasons but callbacks effectively extend them!

Use this 1-san:
— One thread per core or more when being DDoSed.
— Each thread has a vector of non-blocking (a.k.a. asynchronous) sockets.
— Threads iterate on the vector and process a socket when it is ready. Basically you're emulating select but in a more efficient way.

dubs check em

>>11
nice dubs

http://www.aosabook.org/en/nginx.html

Seems a little bullshitty though

I recently wrote

how well will it hold up against say 1000 people

Why don't you simply measure that?

>>13
4chan uses it.

>>15
And 4chan is shit, point proven