The “top” command may help towards this, it does not have CPU-grouped list of threads but rather you can see the list of threads (probably for a single process) and which CPU cores the threads are running on by top -H -p {PROC_ID} then pressing f to go into field selection, j to enable the … Read more
Quartz is an order of magnitude more complex than Spring’s built in scheduler, including support for persistent, transactional and distributed jobs. It’s a bit of a pig, though, even with Spring’s API support. If all you need to is to execute methods on a bean every X seconds, or on a cron schedule, then @Scheduled … Read more
As pointed out by Remus Rusanu, PowerShell would be the way to go. Here’s a simple one-liner that you can use to create a scheduled task, without needing to write a separate .ps1 file: powershell -ExecutionPolicy Bypass -Command Invoke-WebRequest ‘http://localhost/cron.aspx’ -UseBasicParsing Note that line breaks are added only for clarity in all of these command … Read more
It turned out that I could not use the @Scheduled annotation, but I implemented a work-around. In the JavaDoc of the SchedulingConfigurer it is stated that: [SchedulingConfigurer is] Typically used for setting a specific TaskScheduler bean to be used when executing scheduled tasks or for registering scheduled tasks in a programmatic fashion as opposed to … Read more
You can’t do this in pure java. But if you really need it — you can use JNI to call native code which do the job. This is the place to start with: http://ovatman.blogspot.com/2010/02/using-java-jni-to-set-thread-affinity.html http://blog.toadhead.net/index.php/2011/01/22/cputhread-affinity-in-java/ UPD: After some thinking, I’ve decided to create my own class for this: ThreadAffinity.java It’s JNA-based, and very simple — … Read more
You can use the cancel() method on Future. From the javadocs of scheduleAtFixedRate Otherwise, the task will only terminate via cancellation or termination of the executor Here is some example code that wraps a Runnable in another that tracks the number of times the original was run, and cancels after running N times. public void … Read more
The OS sets up a hardware timer (Programmable interval timer or PIT) that generates an interrupt every N milliseconds. That interrupt is delivered to the kernel and user-code is interrupted. It works like any other hardware interrupt. For example your disk will force a switch to the kernel when it has completed an IO.
Yes there is. In fact, there are two separate ways to do it 🙂 Right now, the best way to accomplish what you want is to do the following: Add the parameter isolcpus=[cpu_number] to the Linux kernel command line from the boot loader during boot. This will instruct the Linux scheduler not to run any … Read more
tl;dr Any exception escaping your run method halts all further work, without notice. Always use a try-catch within your run method. Try to recover if you want scheduled activity to continue. @Override public void run () { try { doChore(); } catch ( Exception e ) { logger.error( “Caught exception in ScheduledExecutorService. StackTrace:\n” + t.getStackTrace() … Read more
Answer Modify your Tuesday cron logic to execute every other week since the epoch. Knowing that there are 604800 seconds in a week (ignoring DST changes and leap seconds, thank you), and using GNU date: 0 6 * * Tue expr `date +\%s` / 604800 \% 2 >/dev/null || /scripts/fortnightly.sh Aside Calendar arithmetic is frustrating. … Read more