On 4 Jan '07, at 3:33 PM, Greg Hulands wrote:
I would like to help out on this effort as I write a open source
connection framework for Mac OS X that uses libssh2 for the sftp
transfers. We have the problem that it pegs our worker thread to 100%
of the cpu when using sftp.
That doesn't sound right. Blocking I/O shouldn't consume any more CPU
than non-blocking. If the worker thread is blocked waiting for data to
arrive (or be sent), it should be inside a system call, probably
read(), consuming no CPU.
You could post a sample of your process while it's in this state. Are
you sure it's not some other thread doing a spin-loop waiting for the
SFTP thread to do something?
--Jens
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
libssh2-devel mailing list
libssh2-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libssh2-devel
