So you mention getting a larger db, do you only run one? How large is it? What type of mem/proc do you use and drives? Do you know if the bottleneck is drive access or the MySql program itself?
And, have you ever tried postgresql?
I am just a curious network/web guy working on a site.
Brgds
if it isn't that hard then just go and tell everyone you will do it yourself
I know that i have much better things to do than start trading address space and trying to setup a renumbering just to save a few routes here and there.
ISP are just what they say they are, they can spend all the money they want on routers so i am not woried about it, hell, I have heard that the net couldn't get above " x " number or routes or certain parts would fall off, but lets think about it. Do you really think that isp " x " is going to allow themselves to loose revenue on a " problem " they know is there. If they cannot figure out their router is about to fall over then they should not be in the isp business. I would be nice if the internet was a " proper " network, and maybe through some miracle it will be on day . However, the current net as we know it was never designed to scale like this and move traffic like it does so all of us network designers will have to get the heck over it!!!!!!
This is pointless, why burden the server with extra crap when it can be done at the router. All you need is a cisco router with 12.0 enterprise code. You can set limits on how many half open connections you allow at a time. Then when that limit is reached it will prune them back to a pre-determined number.
Or you can use a " transparent proxy " of sorts that does the same thing on the same router. It will take the syn on behalf of the server, send the syn ack, and if it is legit, put them back together.
Both of these processes are totally transparent to both the server and client.
Just my 2 cents
I noticed that there was a comment about " router configs for such logging " . Anyway , I do router and switch configs on a daily basis. Logging would put a huge strain on a router and slow down the response of routing request. I feel that logging would be better done on a transparent proxy or a firewall. You can scale the hardware to suit this need ( more processors and such ). Routers usually have somewhat week cpu's ( and don't really need anymore as long as you don't put logging and such on it ). Just my 2 cents worth.
So you mention getting a larger db, do you only run one? How large is it? What type of mem/proc do you use and drives? Do you know if the bottleneck is drive access or the MySql program itself? And, have you ever tried postgresql? I am just a curious network/web guy working on a site. Brgds
if it isn't that hard then just go and tell everyone you will do it yourself I know that i have much better things to do than start trading address space and trying to setup a renumbering just to save a few routes here and there. ISP are just what they say they are, they can spend all the money they want on routers so i am not woried about it, hell, I have heard that the net couldn't get above " x " number or routes or certain parts would fall off, but lets think about it. Do you really think that isp " x " is going to allow themselves to loose revenue on a " problem " they know is there. If they cannot figure out their router is about to fall over then they should not be in the isp business. I would be nice if the internet was a " proper " network, and maybe through some miracle it will be on day . However, the current net as we know it was never designed to scale like this and move traffic like it does so all of us network designers will have to get the heck over it!!!!!!
This is pointless, why burden the server with extra crap when it can be done at the router. All you need is a cisco router with 12.0 enterprise code. You can set limits on how many half open connections you allow at a time. Then when that limit is reached it will prune them back to a pre-determined number. Or you can use a " transparent proxy " of sorts that does the same thing on the same router. It will take the syn on behalf of the server, send the syn ack, and if it is legit, put them back together. Both of these processes are totally transparent to both the server and client. Just my 2 cents
I noticed that there was a comment about " router configs for such logging " . Anyway , I do router and switch configs on a daily basis. Logging would put a huge strain on a router and slow down the response of routing request. I feel that logging would be better done on a transparent proxy or a firewall. You can scale the hardware to suit this need ( more processors and such ). Routers usually have somewhat week cpu's ( and don't really need anymore as long as you don't put logging and such on it ). Just my 2 cents worth.