How much cpu does your server use when it's polling those 1000 connections?

I ask, because think that you may be misinterpreting the results of your profiling.

What the profiling shows is that your program is spending 56% of elapsed wall-clock time in the can_read() call, but so what? You are not using a timeout value, which means that if there is nothing to do, no input to read, then that call waits until there is. What else would you have it do?

Unless you are thrashing your cpu, that is probably exactly where you want it to wait whilst there is nothing to do so that it is instantly read to roll as soon as there is.

If you are thrashing the cpu that is a different matter, but that is not reflected or demonstrated in the profiler output.

In that case, it may be that the implementation of IO::Select or the underlying calls on your system is such that whilst there is nothing avialable to read, it sits in a tight loop--like cartoon kids on a road trip:Are we there yet? Are we there yet? Are we there yet?--, and that is the cause of the thrashing.

In that case, it might be better to add a timeout to the can_read() call and explicitly sleep a little if there is nothing to do.

sub ckSockets {
... CHECK:
    my @breadys = $io_select_obj->can_read( 0.01 );
    unless( @breadys ) {
        usleep( 0.1 ); ## See Time::HiRes
        ## Or select undef, undef, undef, 0.1; 
        ## but that might be a "busy loop" also.
        goto CHECK;
    }
...
}
[download]

But, unless you are experiencing high cpu loads when there is little or no traffic, then can_read() is exactly the right place for you program to spend most of it's time whilst it waits for something to do. Good on you for profiling, but be sure you are interpreting the results correctly.