On Wednesday, February 10, 2016 07:56:40 AM Thomas Eckardt wrote: > >Is this to be expected and/or temporary condition or > >possibly another issue? > > This is expected on a single or dual core system (both are not recommended > with V2 - use at least four cores).
That is really an insane requirement and really need to revisit ASSP entirely and scale down its requirements. Enterprise Java applications servers such as Glassfish and JBoss/Wildfy do not have such processor requirements. These are the days of vms and instances, many in cloud environments. I have ran ASSP fine on single and dual core. I just went back to single since I am deploying more than one. Reasons why many run say lighttpd or nginx over Apache, for minimal overhead. For the price of a 4 core vm, I could have 2 dual core or 4 1 core and have lots of redundancy. Having 2 or more 4 core systems for ASSP can start to drive up costs. I recall back in the day using Spamassassin, ClamAV, qmail scanner, and I think some other stuff. System resource usage was stupid per email for processing. Part of the reason I switched to ASSP long ago. It performed very well and had considerably less resources. Now seem to have gone the complete opposite direction. None the less I am running it just fine as a minimal experiment in 1 core 1GB vms in public clouds. The 1GB memory was an issue for only rebuilding spam db, as that would crash. Adding on 1GB of swap corrected that issue. Crashing stopped per rebuilding the spam db. I have to confirm if it still crashes when reporting spam via email interface. No ticket, because I am sure it would be close as invalid/wontfix etc and something about being below ASSP minimal requirements. > If 2.4.7 16036 is started the first time, some (hidden) corrections to the > whitelistdb (and possibly other lists) will be done. > Depending on the size and the implementation of the databases and lists, > this may take 1 to 3 minutes - typicaly these tasks are finished within > some seconds. > These tasks are all running only on one thread - each after eachother. > > There are currently (at least) running 280 installations on build 16036 - > noone else has this problem reported. Just because problems do not get reported do not mean they do not exist at times. I would be hesitant to report and open any tickets because of the unwillingness to want to hear a different point of view and have ASSP maybe evolve in other more universal ways. Not to mention might get blamed on something stupid and pathetic like, your splitting up ASSP and its not installed in a single directory for everything. I have talked to several long time perl developers I know. I cannot get them to even contribute or help.... They all complain about how its 1 single file and a huge mess... Really needs to have more than one perl file, or more modules. If your wanting others to help contribute, etc. There are many reasons why things may not get reported, at least in my case. Normally I am big on opening tickets, and filing bugs. When projects are receptive to such. -- William L. Thomson Jr. Obsidian-Studios, Inc. http://www.obsidian-studios.com ------------------------------------------------------------------------------ Site24x7 APM Insight: Get Deep Visibility into Application Performance APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month Monitor end-to-end web transactions and take corrective actions now Troubleshoot faster and improve end-user experience. Signup Now! http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140 _______________________________________________ Assp-user mailing list Assp-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/assp-user