On Wed, Jan 14, 2009 at 5:58 PM, Fred Moore <[email protected]> wrote: > Niklas, All, > > we observed a long (about 1 minute) plateau of 100% CPU when trying to > setPorts() in > org.apache.ftpserver.DefaultDataConnectionConfiguration$Passive with "wide" > port ranges such as 2122-65535. We observed that FTPServer internally > performs an apparently very expensive scan on this range. > > This has been seen on an M2-ish FTPServer codebase on Windows, it may apply > to latest codebases and other platforms but I'm not sure of this.
Yeah, the implementation of this part, in short, sucks. > Can this be made less CPU intensive and quicker (to shorten server downtime > and reduce resource consumption in production)? It sure can, lets address this in 1.0.1 > I created https://issues.apache.org/jira/browse/FTPSERVER-264 to cover this. Thanks! /niklas
