• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

Performance improvement for AES

 
Greenhorn
Posts: 6
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi Folks,

We are using AES 256 encryption algorithm but when we measure CPU utilization; we were stunned to find 100%.

Then I have tried with all available algorithms like AES 192, AES 128 and others.
Every algo has different CPU utilization like avg 65%, 63% resp.

Kindly note that the file I used for to encrypt is simple .xml file not more than 100 KB. It shows 100% for AES 256 for a period of execution only means till the file gets encrypted.

If we must have to use AES 256 only then is there any way to reduce that 100% to at least 70 or 80 % as 100% CPU utlization is not advisible.

Your tips are highly appreciated.

With best regards.
 
Rancher
Posts: 43081
77
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Why wouldn't you want utilization to be 100%? Anything less means that the encryption isn't done as quickly as it could be. I'm guessing you have other processes that you don't want to starve of CPU time, but the task scheduler should take care that other processes of the same priority keep running as well. If you have other Java tasks in the same JVM that have higher priority, consider running the encryption as its own thread; then you can fiddle around with the thread priority.
 
reply
    Bookmark Topic Watch Topic
  • New Topic