I grep'd the source directory for CLUS (clus) and the only thing all the interesting I found was the define in report.c; "report.c:#define MAX_NUM_CLUSTERS 16"
I changed this to 32 and it seems OK! Couple more questions: 1.) Is this the only change required - or is there something sneaky somewhere? 2.) I "need" about 180 clusters; would this be "bad", really bad, or OK? 3.) Should I use network flows to see aggregate info instead? Last resort is to break up my ntop instances even further so I have < 32 sites / instance, each "site" would then be a cluster. Ideally Host Clusters would be interface significant instead of the current instance significant - make sense? I'll make a new post on that thought... ________________________________ From: Gary Gatten Sent: Tuesday, May 19, 2009 10:44 AM To: '[email protected]'; '[email protected]' Subject: Increasing the Host Cluster limit of 16 How hard would it be to bump this to 32, 64, etc. and what are the impacts? I'm assuming more memory and cpu time, but is it "significant"? <font size="1"> <div style='border:none;border-bottom:double windowtext 2.25pt;padding:0in 0in 1.0pt 0in'> </div> "This email is intended to be reviewed by only the intended recipient and may contain information that is privileged and/or confidential. If you are not the intended recipient, you are hereby notified that any review, use, dissemination, disclosure or copying of this email and its attachments, if any, is strictly prohibited. If you have received this email in error, please immediately notify the sender by return email and delete this email from your system." </font>
_______________________________________________ Ntop mailing list [email protected] http://listgateway.unipi.it/mailman/listinfo/ntop
