The directives are for tuning both single and multiprocessor systems. They are not meant as a tradeoff. Some multiprocessor systems do not exhibit the reported sleep for 30 seconds behavior. We have not been able to reproduce
it ourselves.

I can produce it on my machine even on version 3.0.4.4. David was also provided remote access to my machine and seen this issue occur when I first reported it under the early beta.

It's hard to fix something that we can't reproduce but we will keep
trying.  It's not even clear to me that this problem still exists in the
latest version.

I posted earlier (and to the [EMAIL PROTECTED]) that the problem still exists in the latest beta. Again, I can provide remote access to this machine if needed. You can mitigate the effects of this issue by adjusting the waitformail, but it seems to cause more cpu related usage.

What concerns me even more than the obvious issue with multiprocessor machines is its excessive use of CPU. This is also included in my beta notes.

Darrell


-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Andy Schmidt
Sent: Thursday, September 22, 2005 7:56 PM
To: Declude.Virus@declude.com
Subject: RE: [Declude.Virus] Declude Beta 3.0.4.4 Posted

Hi David,

I can't help but ask...

You are proposing options that will "help" with the dual processor issue.
But, are you REPRODUCING the issue and fixing it? I understand that the
problem is that the service goes to sleep for 30 seconds, even though there
are messages in the PROC folder. Clearly that should not happen.  Changing
the "timings" will only create a trade-off by consuming extra
machine-resources.

Even on a dual-processor system should the service be able to determine
reliably if a folder has content or not?

I'm just worried that the beta is declared "successful" when an entire class
of machines is only working with a bandage.

Best Regards
Andy Schmidt

Phone:  +1 201 934-3414 x20 (Business)
Fax:    +1 201 934-9206


-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of David Barker
Sent: Thursday, September 22, 2005 12:28 PM
To: Declude.Virus@declude.com
Subject: RE: [Declude.Virus] Declude Beta 3.0.4.4 Posted

Yes, these are to help adjust for timing with Dual-proc

Different systems / configuration respond differently to these settings.

In particular they to fine tune through-put with CPU utilization.

1. SLOW server that is heavily loaded

You may want to try to increase WAITBETWEENTHREADS and lower THREADS.

2. FAST server
Use the THREADS and WAITFORTHREADS to adjust the CPU utilization.

When decludeproc first starts up it will use a lot of the CPU but after that
the %CPU used by decludeproc should come way down.

The %CPU of all processes running may be high depending on external tests,
other processes, etc.  If the system is spiking but coming down quickly
that's good.

David B
www.declude.com

-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Keith Johnson
Sent: Thursday, September 22, 2005 12:27 PM
To: Declude.Virus@declude.com
Subject: RE: [Declude.Virus] Declude Beta 3.0.4.4 Posted

David,
Are these to be used to correct issues with Dual-proc, or is that
still an ongoing issue still be looking at?  Thanks for the time.

Keith

-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of David Barker
Sent: Thursday, September 22, 2005 11:41 AM
To: Declude.JunkMail@declude.com; Declude.Virus@declude.com
Subject: [Declude.Virus] Declude Beta 3.0.4.4 Posted


2 new Directives

WAITFORTHREADS      1500
Located in the Declude.cfg - Defined in milliseconds eg. 1500 = 1.5 seconds
this can be changed so that when the maximum threads are in use this time
specifics the wait before checking to launch more threads.

WAITBETWEENTHREADS         1
Located in the Declude.cfg - Defined in milliseconds eg. 1 = 1 millisecond
The time to wait between spawning one thread and starting to process another
thread.

David B
www.declude.com

---
This E-mail came from the Declude.Virus mailing list. To unsubscribe, just
send an E-mail to [EMAIL PROTECTED], and
type "unsubscribe Declude.Virus".    The archives can be found
at http://www.mail-archive.com.
---
This E-mail came from the Declude.Virus mailing list. To unsubscribe, just
send an E-mail to [EMAIL PROTECTED], and
type "unsubscribe Declude.Virus".    The archives can be found
at http://www.mail-archive.com.

---
This E-mail came from the Declude.Virus mailing list. To unsubscribe, just
send an E-mail to [EMAIL PROTECTED], and
type "unsubscribe Declude.Virus".    The archives can be found
at http://www.mail-archive.com.

---
This E-mail came from the Declude.Virus mailing list.  To
unsubscribe, just send an E-mail to [EMAIL PROTECTED], and
type "unsubscribe Declude.Virus".    The archives can be found
at http://www.mail-archive.com.

--
No virus found in this incoming message.
Checked by AVG Anti-Virus.
Version: 7.0.344 / Virus Database: 267.11.3/107 - Release Date: 9/20/2005


--
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.344 / Virus Database: 267.11.3/107 - Release Date: 9/20/2005


---
This E-mail came from the Declude.Virus mailing list.  To
unsubscribe, just send an E-mail to [EMAIL PROTECTED], and
type "unsubscribe Declude.Virus".    The archives can be found
at http://www.mail-archive.com.


---
This E-mail came from the Declude.Virus mailing list.  To
unsubscribe, just send an E-mail to [EMAIL PROTECTED], and
type "unsubscribe Declude.Virus".    The archives can be found
at http://www.mail-archive.com.

Reply via email to