[Assp-test] Antwort: Re: fixes and changes in assp 2.0.2_3.2.25

[Thomas E. <Tho...@th...>]

>at this point is it faster to run ASSP with 5.12

Huuu... ???? .... NO!

First - ASSP V2 is running very well with Perl 5.12.4 on my systems. It 
uses less memory and is faster than on Perl 5.10.X !
Using 5.14, the memory usage will be much less than on 5.12. And ASSP will 
be even faster. 

BUT !!! 
Using Perl 5.14.1, I get unexpected crashes (no log, nothing to see) of 
Perl (1-3 a day). I'm currently unable to say what the reason is.
My first choice was the regex engine of 5.14, which contains major changes 
to 5.12 - and for this reason I've disabled the ASSP regex optimizer for 
installations on Perl 5.14 (this could be changed back in future). The 
internal regex optimization of Perl 5.14 is very good - so you'll not see 
major differences using the ASSP optimizer.

My second choice was (is) the DBD::mysql driver (Windows) . This needs 
some more testing, the reason could be also any other XS code/module.
I don't think that Perl 5.14 has any general problem with ASSP - I assume, 
that this issue is related anyhow to my system configuration or 
installation.

So 5.12.4 will be fine for you Ken - 5.14.1 will be better - let's see how 
it is running on your system.

Thomas







Von:    K Post <nnt...@gm...>
An:     ASSP development mailing list <ass...@li...>
Datum:  25.09.2011 13:26
Betreff:        Re: [Assp-test] fixes and changes in assp 2.0.2_3.2.25




If regex optimiztion is skipped for perl 5.14+, at this point is it faster
to run ASSP with 5.12?

We haven't updated yet, but were about to.  We won't if you recommend the
older version still.

Thanks

On Sat, Sep 24, 2011 at 5:21 AM, Thomas Eckardt
<Tho...@th...>wrote:

> Hi all,
>
> fixed in 2.0.2_3.2.25:
>
> - the mail header parsing was not working correct in several features
> - unexpected signals SIGALARM are now captured
> - some minor code improvements
> - some optimization for Perl 5.14
> - some optimization for BerkeleyDB
> - if assp.cfg was modified outside assp with an UTF-8 compatible editor
> and an UTF-8 BOM was written to the file, assp was no longer starting
>
>
>
> changed:
>
> - if used, AsspSelfLoader.pm 2.03 is required
> - the regex optimization is skipped, if assp is running on Perl 5.14 or
> higher
>
> Thomas
>
> DISCLAIMER:
> *******************************************************
> This email and any files transmitted with it may be confidential, 
legally
> privileged and protected in law and are intended solely for the use of 
the
>
> individual to whom it is addressed.
> This email was multiple times scanned for viruses. There should be no
> known virus in this email!
> *******************************************************
>
>
>
>
> 
------------------------------------------------------------------------------
> All of the data generated in your IT infrastructure is seriously 
valuable.
> Why? It contains a definitive record of application performance, 
security
> threats, fraudulent activity, and more. Splunk takes this data and makes
> sense of it. IT sense. And common sense.
> http://p.sf.net/sfu/splunk-d2dcopy2
> _______________________________________________
> Assp-test mailing list
> Ass...@li...
> https://lists.sourceforge.net/lists/listinfo/assp-test
>
>
------------------------------------------------------------------------------
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security
threats, fraudulent activity, and more. Splunk takes this data and makes
sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2dcopy2
_______________________________________________
Assp-test mailing list
Ass...@li...
https://lists.sourceforge.net/lists/listinfo/assp-test




DISCLAIMER:
*******************************************************
This email and any files transmitted with it may be confidential, legally 
privileged and protected in law and are intended solely for the use of the 

individual to whom it is addressed.
This email was multiple times scanned for viruses. There should be no 
known virus in this email!
*******************************************************