Ahhh, The CU usage is *always* going to go to 100 percent, no matter how low the priority is. The real question should have been "when I sign or encrypt, the operation adversly affects other important processes because the s/e operation is consuming needed cpu cycles, what can I do about this". Assuming this *is* a good paraphase of the problem, then setting the thread priority is the correct solution, noting that CPU will still always be at 100 percent, but other processes will be unaffected......
must be picky monday ;) -lee -----Original Message----- From: Ken Hirsch [mailto:[EMAIL PROTECTED]] Sent: Monday, July 29, 2002 8:31 AM To: [EMAIL PROTECTED]; [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: Re: CPU usage and SMIME? Maya wrote: >I use Openssl 0.9.6c on Windows 2000. >I use SMIME functions available and created my ATL COM which has 2 main functions >:Encode and Decode. >When I Sign or Encrypt messages with size about 3MB , the CPU usage goes up to >100%. Is it possible something to be done about this? Even if it will slow the > process a little bit? You could lower the priority of the thread that's doing the function with SetThreadPriority(). Ken ______________________________________________________________________ OpenSSL Project http://www.openssl.org User Support Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED] ______________________________________________________________________ OpenSSL Project http://www.openssl.org User Support Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
