Hi!

>I can't decipher this either Mike.

  Mike . . .

 Look on result of Mike behavior:

----- Original Message ----- 
From: "Fritz Borgstedt"
To: "For Users of ASSP"
Sent: Monday, May 20, 2013 5:46 PM
Subject: Re: [Assp-user] rebuild kills assp even with correct perl


I ( Fritz) told you ( Mike) from the beginning,
that I ( Fritz) only support V1 because that is my field of experience.

 VVM: typical answer ( many,many,many,many time . . .):
Mike>> The only information is the cryptic information that Fritz sent me
Mike>>while he was working on the server;

 VVM: and as result:
I ( Fritz) will not longer do any personal support for this list.

Fritz
--

TO Mike: Great anti-thanks from ASSP users!





>
>It would be great if there were a
> clearly defined set of system requirements for starter....
>
> We need BerkeleyDB 5+?
>

 Yes, in any case


> We need 32-bit perl?


Perl 32Bit is _preffered_ by memory usage


> crashes daily due to memory leaks.

  RAM ?  How exactly Mb ?

As variant,  try 64Bit Perl

 Some another Q:

count of workers?

maxbytes ?  4Kb? 8? 16? Or?

 Are You use  MySQL/MS SQL and( or) BerkeleyDB ?

Windows ?  2003 / 2008 R2 ?

or Linux? RedHat / Debian / or ?

> . . . memory




Best regards, Victor Miasnikov
Blog:  http://vvm.blog.tut.by/

P.S.

> system requirements


----- Original Message ----- 
From: "Victor Miasnikov" vvm
To:  . . . ;  "ASSP development mailing list"
Sent: Thursday, March 29, 2012 6:53 PM
Subject: [Assp-test] Use both MySQL ( "DB:") and BerkeleyDB ( for other) <=flat 
files == _terrible_ memory usage Re: 
Antwort: Re:Antwort: Re: Antwort: Memory footprint


Hi!

>> Do you use any DB ?
> No, just flat files.  And, I just checked again.  it's now running at 1.9GB 
> and 112MB swap

 flat files ==   _terrible_ memory usage

 This
VVM>>>Win 2003 x86  720Mb for OS + 1Gb for soft => 5 . . 7 workers ( MySQL ( or 
other SQL Server) + BerkeleyDB
_absolutely_ requred )
may be read as

 If use both MySQL ( "DB:") and BerkeleyDB ( for other) 7 workers ( on x86) use 
608 Mb



Best regards, Victor Miasnikov
--


----- Original Message ----- 
From: "Victor Miasnikov" vvm
To: "PMW Troy"
Cc: "ASSP development mailing list"
Sent: Friday, March 23, 2012 2:38 PM
Subject: Re: [Assp-test] ASSP V2 Problem Worker_X accept to client failed





 . . .


Thomas Eckardt>> - too high setting for 'maxbytes'

"To:" PMW Troy:
 maxbytes ?  4Kb? 8? 16? Or?


> says 5 workers are active.

Try 7 workers if have free RAM  and( or) try RAM-Dirve for TMPDb
Try 3 workers in case small size RAM


> I will try updating to perl 5.12, and see if that helps.


 And even to 5.14 . . . <= in case small size RAM


Best regards, Victor Miasnikov
Blog:  http://vvm.blog.tut.by/

P.S.

Thomas Eckardt>> - bad system design - too less RAM (min 1GB of the non system 
part)

 Yes: for example: Win 2003 x86  720Mb for OS + 1Gb for soft => 5 . . 7 workers 
( MySQL ( or other SQL Server) + 
BerkeleyDB _absolutely_ requred )

Thomas Eckardt>> and/or CPU cores (min 4)
PMW Troy:>
PMW Troy> I would suggest adding those minimums to the archive, because this is
PMW Troy> the first I've heard of them, especially the minimum 4 core part.

First of all, more than 1 (one) CPU core

2 core is absolutly(!) minimum

4 core is _recommended_ , but in any case close to minimum
( and see in P.P.P.S.  if  "use of virtualization ( Hyper-V / XEN / ESX / 
etc.)"  -- count of CPU is not big problem)


P.P.S.

PMW Troy:> first I've heard . . .

 Don't forgot about storage subsystem ( HDD / RAID) :


----- Original Message ----- 
From: "Thomas Eckardt"
To: "ASSP development mailing list"
Sent: Monday, November 21, 2011 8:44 PM
Subject: [Assp-test] Antwort: best config for rebuildspam and HMM

  . . .

There are multiple possible reasons for such a slowness. I think, slow IO
performance is the reason in your case. BerkeleyDB (use for the temporary
HMM DB's) needs a very fast IO system, in case large DB's like HMM are
processed.

 . . .

It is not important that the IO system could process many MB/s - IO/s is
much more important.

 . . .

My IO system (in an ESX server) for assp is designed as follows.

- LSI high performance SAS-CTL with 256 MB Cache
- 6 disks each with 10Krpm in a RAID10

--


P.P.P.S.

> We're a small business

 I strongly recommend the use of virtualization ( Hyper-V / XEN / ESX / etc.) , 
especially for small businesses: 
consolidation costs / better TCO





--





----- Original Message ----- 
From: "Thomas Eckardt"
To: "ASSP development mailing list"
Sent: Wednesday, March 21, 2012 7:11 PM
Subject: [Assp-test] Antwort: ASSP V2 problem Worker_x accept to clientfailed




These are the most common reasons:

- bad system design - too less RAM (min 1GB of the non system part) and/or
CPU cores (min 4)
- the memory of the assp processes is paged
- too slow DNS-servers are used ( fast local DNS servers are recommended)
- a too slow database server is used (seems some MSSQL-setup,drivers....
makes problems because of uncleaned DB-cursors - use MySQL instead)
- regular expressions are looping or taking too long to process
- too high setting for 'maxbytes'
- too less workers (5-7/9) - highload systems with more than 300.000
connection per day could require a special/professional setup and system
design
- Perl modules are not uptodate - Perl 5.12 or higher is recommended

Thomas
-- 


------------------------------------------------------------------------------
AlienVault Unified Security Management (USM) platform delivers complete
security visibility with the essential security capabilities. Easily and
efficiently configure, manage, and operate all of your security controls
from a single console and one unified framework. Download a free trial.
http://p.sf.net/sfu/alienvault_d2d
_______________________________________________
Assp-user mailing list
Assp-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/assp-user

Reply via email to