Okay, figure this out:

Since Update 10, Oracle's Java SE 6.0 comes with a tool called "Java 
Quick Starter" (JQS). Its purpose? To speed up starting Java software, 
by loading the most commonly used stuff ahead of time.

And loading ahead of time it does.

It does this not only once though, but - for whatever sake - every 
bloody hour. Over and over again. The same bloody files. Which on my 
system (maybe due to a sinister conspiration with the Anti-Virus 
software I use) takes about 1 or 2 /minutes/ each time. Oh, and did I 
mention that all this time it starves every other piece of software 
running from hard disk I/O?

Heck, maybe it /does/ speed up startup of Java software, but seriously:

*I DON'T GIVE A BLOODY DAMN!*


Did I mention that the official procedure how to turn off this bullshit 
mysteriously doesn't work on my machine? >_<

(Fortunately I stayed resolute and resourceful in an atmosphere of utter 
pessimism...)

Post a reply to this message

On 06/03/2011 05:30 PM, clipka wrote:
> Okay, figure this out:
>
> Since Update 10, Oracle's Java SE 6.0 comes with a tool called "Java
> Quick Starter" (JQS). Its purpose? To speed up starting Java software,
> by loading the most commonly used stuff ahead of time.
>
> And loading ahead of time it does.
>
> It does this not only once though, but - for whatever sake - every
> bloody hour. Over and over again. The same bloody files. Which on my
> system (maybe due to a sinister conspiration with the Anti-Virus
> software I use) takes about 1 or 2 /minutes/ each time. Oh, and did I
> mention that all this time it starves every other piece of software
> running from hard disk I/O?
>
> Heck, maybe it /does/ speed up startup of Java software, but seriously:
>
> *I DON'T GIVE A BLOODY DAMN!*
>
>
> Did I mention that the official procedure how to turn off this bullshit
> mysteriously doesn't work on my machine? >_<

and I bet it's documentation sux too ;-)

>
> (Fortunately I stayed resolute and resourceful in an atmosphere of utter
> pessimism...)

lol then ... I admire your half full glass (rather than empty) outlook 
on things!

Post a reply to this message

Am 03.06.2011 23:40, schrieb Jim Holsenback:
>> Did I mention that the official procedure how to turn off this bullshit
>> mysteriously doesn't work on my machine? >_<
>
> and I bet it's documentation sux too ;-)

Documentation?? *What* documentation??

>> (Fortunately I stayed resolute and resourceful in an atmosphere of utter
>> pessimism...)
>
> lol then ... I admire your half full glass (rather than empty) outlook
> on things!

Yeah; those 1-2 minutes an hour have been pestering me for months now, 
until today I finally managed to identify the culprit... and nail it down.

*WIN!*

Post a reply to this message

clipka <ano### [at] anonymousorg> wrote:
> (Fortunately I stayed resolute and resourceful in an atmosphere of utter 
> pessimism...)

  Someone has been playing too much... :P

-- 
                                                          - Warp

Post a reply to this message

On 03/06/2011 09:30 PM, clipka wrote:

> Since Update 10, Oracle's Java SE 6.0 comes with a tool called "Java
> Quick Starter" (JQS). Its purpose? To speed up starting Java software,
> by loading the most commonly used stuff ahead of time.
>
> And loading ahead of time it does.

I'm pretty sure JQS has been there for years. Lots of software does this 
(e.g., Acrobat Reader). The idea, presumably, is to load stuff into 
memory ahead of time.

Except that isn't this the entire point of the Windows prefetch cache? 
Also, won't the unused data simply get swapped back out to disk after a 
while? (Thus utterly defeating the entire purpose of it.) Unless you 
lock the pages in memory - in which case you're taking resources away 
from applications that *definitely* need to run in order to benefit an 
application which *might* need to run at some unspecified future point.

Personally, I dislike quick-starter services. They're a waste of resources.

> It does this not only once though, but - for whatever sake - every
> bloody hour. Over and over again. The same bloody files. Which on my
> system (maybe due to a sinister conspiration with the Anti-Virus
> software I use) takes about 1 or 2 /minutes/ each time. Oh, and did I
> mention that all this time it starves every other piece of software
> running from hard disk I/O?

OK, that's pretty screwed up. It shouldn't take anywhere near that long. 
(Unless your AV product is decompressing all the JAR files to check 
there's no viruses inside them...)

> Did I mention that the official procedure how to turn off this bullshit
> mysteriously doesn't work on my machine? >_<

It's news to me that there's even an official procedure to turn it off...

> (Fortunately I stayed resolute and resourceful in an atmosphere of utter
> pessimism...)

Outstanding! You <subject name here> must be the pride of <subject 
hometown here>.

-- 
http://blog.orphi.me.uk/
http://www.zazzle.com/MathematicalOrchid*

Post a reply to this message

On 04/06/2011 07:31 AM, Warp wrote:
> clipka<ano### [at] anonymousorg>  wrote:
>> (Fortunately I stayed resolute and resourceful in an atmosphere of utter
>> pessimism...)
>
>    Someone has been playing too much... :P

What is this "too much" concept of which you speak? ;-)

-- 
http://blog.orphi.me.uk/
http://www.zazzle.com/MathematicalOrchid*

Post a reply to this message

On 04/06/2011 07:31 AM, Warp wrote:

>    Someone has been playing too much... :P

http://www.thinkgeek.com/homeoffice/mugs/c7cc/action/215f43a/?cpg=160SS

-- 
http://blog.orphi.me.uk/
http://www.zazzle.com/MathematicalOrchid*

Post a reply to this message

> On 03/06/2011 09:30 PM, clipka wrote:
>
>> Since Update 10, Oracle's Java SE 6.0 comes with a tool called "Java
>> Quick Starter" (JQS). Its purpose? To speed up starting Java software,
>> by loading the most commonly used stuff ahead of time.
>>
>> And loading ahead of time it does.
>
> I'm pretty sure JQS has been there for years. Lots of software does this
> (e.g., Acrobat Reader). The idea, presumably, is to load stuff into
> memory ahead of time.
I don't know how long, but I think that it was there with Java SE 5.x.

>
> Except that isn't this the entire point of the Windows prefetch cache?
> Also, won't the unused data simply get swapped back out to disk after a
> while? (Thus utterly defeating the entire purpose of it.) Unless you
> lock the pages in memory
OR you reload the stuff periodicaly to reinitiate the countdown...

- in which case you're taking resources away
> from applications that *definitely* need to run in order to benefit an
> application which *might* need to run at some unspecified future point.
>
> Personally, I dislike quick-starter services. They're a waste of resources.
I share your opinion on those. I hunt them down, and kill them, as much 
as I can.

>
>> It does this not only once though, but - for whatever sake - every
>> bloody hour. Over and over again. The same bloody files. Which on my
>> system (maybe due to a sinister conspiration with the Anti-Virus
>> software I use) takes about 1 or 2 /minutes/ each time. Oh, and did I
>> mention that all this time it starves every other piece of software
>> running from hard disk I/O?
>
> OK, that's pretty screwed up. It shouldn't take anywhere near that long.
> (Unless your AV product is decompressing all the JAR files to check
> there's no viruses inside them...)
1 - It reloads the files to prevent them been pushed on the page file.
2 - The AV is to agressive. Scanned files should be remembered, and, 
unless they have been changed, skipped on the next scan.
3 - Yes, the AV need to uncompress and extract files from any archive if 
it wants to scan it's content. JARs are compressed archives.

>
>> Did I mention that the official procedure how to turn off this bullshit
>> mysteriously doesn't work on my machine? >_<
>
> It's news to me that there's even an official procedure to turn it off...
>
>> (Fortunately I stayed resolute and resourceful in an atmosphere of utter
>> pessimism...)
>
> Outstanding! You <subject name here> must be the pride of <subject
> hometown here>.
>

If it's impossible to turn JQS off, then you kill the process, then you 
delete JQS.exe.

Post a reply to this message

>> Personally, I dislike quick-starter services. They're a waste of
>> resources.
> I share your opinion on those. I hunt them down, and kill them, as much
> as I can.

If it works as intended, it's making one application faster by making 
every other application in the system slower. How selfish is that?

> 2 - The AV is to agressive. Scanned files should be remembered, and,
> unless they have been changed, skipped on the next scan.

Don't you just love the way most AV product insist on down periodic 
manual scans?

1. If a file is never opened, it doesn't *matter* how's inside it. It 
can't possibly run.

2. If a file is opened, the on-demand scanner will scan it anyway. 
There's no need to do a manual scan as well.

3. I've yet to see any AV product which "remembers" which files it's 
scanned and stops rescanning them unless they changed. (Presumably 
because that would make it too easy for a virus to slip past; just tweak 
the file timestamp...)

For that matter, I've yet to see an AV product that's any good at 
*removing* malware. Most of them will *detect* an infection, but they do 
an utterly crap job of *removing* it.

> 3 - Yes, the AV need to uncompress and extract files from any archive if
> it wants to scan it's content. JARs are compressed archives.

A Jar file is just a Zip file. (Actually, a surprising number of files 
are just orginary Zip files...) But yes, if it's loading a lot of Jar 
files, that would explain it. I don't know what JQS is loading. Maybe 
just [uncompressed] executable files, IDK.

> If it's impossible to turn JQS off, then you kill the process, then you
> delete JQS.exe.

That's probably not an especially good idea; the product repair routine 
will probably restore it for you.

Actually, I just checked my system. JQS is a normal Windows service. 
Just configure it to not run at startup. Done.

-- 
http://blog.orphi.me.uk/
http://www.zazzle.com/MathematicalOrchid*

Post a reply to this message

>>> Personally, I dislike quick-starter services. They're a waste of
>>> resources.
>> I share your opinion on those. I hunt them down, and kill them, as much
>> as I can.
>
> If it works as intended, it's making one application faster by making
> every other application in the system slower. How selfish is that?
>
>> 2 - The AV is to agressive. Scanned files should be remembered, and,
>> unless they have been changed, skipped on the next scan.
>
> Don't you just love the way most AV product insist on down periodic
> manual scans?
>
> 1. If a file is never opened, it doesn't *matter* how's inside it. It
> can't possibly run.
>
> 2. If a file is opened, the on-demand scanner will scan it anyway.
> There's no need to do a manual scan as well.
>
> 3. I've yet to see any AV product which "remembers" which files it's
> scanned and stops rescanning them unless they changed. (Presumably
> because that would make it too easy for a virus to slip past; just tweak
> the file timestamp...)
Avast does it. It have a local database of files scanned and found sane. 
They are excluded from autoscans for a set, and configurable, duration. 
They are NOT excluded from scheduled and manual scans.

>
> For that matter, I've yet to see an AV product that's any good at
> *removing* malware. Most of them will *detect* an infection, but they do
> an utterly crap job of *removing* it.
>
>> 3 - Yes, the AV need to uncompress and extract files from any archive if
>> it wants to scan it's content. JARs are compressed archives.
>
> A Jar file is just a Zip file. (Actually, a surprising number of files
> are just orginary Zip files...) But yes, if it's loading a lot of Jar
> files, that would explain it. I don't know what JQS is loading. Maybe
> just [uncompressed] executable files, IDK.
>
>> If it's impossible to turn JQS off, then you kill the process, then you
>> delete JQS.exe.
>
> That's probably not an especially good idea; the product repair routine
> will probably restore it for you.
>
> Actually, I just checked my system. JQS is a normal Windows service.
> Just configure it to not run at startup. Done.
>

Post a reply to this message