one more question, what is the recommendation for number of worker threads
for single-core and dual-core systems ?
-manoher
On Wed, Sep 22, 2010 at 8:37 PM, Trond Norbye wrote:
> The last thread is the thread running the clock and accepting new
> connections.
>
> Cheers
>
> Trond
>
> Sent from m
Hello All,
Here is a patch against the central repo that adds sFlow monitoring.
Please comment!
http://www.inmon.com/technology/sfmc_20100923.zip
For background on this, please read:
http://blog.sflow.com/2010/08/sflow-host-structures.html
If you compile with this patch, then you can run with "
Any luck resolving this problem?
I'm getting the same error using gcc 3.4.3 and libevent 1.4.14b-stable
on Solaris 10 SPARC.
gcc configured with: /sfw10/builds/build/sfw10-patch/usr/src/cmd/gcc/
gcc-3.4.3/configure --prefix=/usr/sfw --with-as=/usr/ccs/bin/as --
without-gnu-as --with-ld=/usr/ccs/b
Great collection of ideas.
My situation is rather unique. The application is pre production -
means it prepares content
for a production platform. The problem is that it is slow. You would
say - so what, this is pre production.
The issue is that it's done at least once a day sometimes 2-3 time.
E
what about map-reduce? chop the job to much smaller sub-jobs and then
have someone(another server or PC) else to process.
i assume your app probably loads data from a DB, and wont load the 1TB
data and then process it entirely.
doing something kinda like pagination? fetch a chunk and have someone
