After removing default filters from the profiling tool, it was revealed that the work that is being done every ~20 seconds and lasting for 8-10 seconds includes the following functions via the updated thread dump <http://i.stack.imgur.com/NAmc5.png>:
- java.io.WinNTFileSystem.canonicalize0 (6-8 seconds) - java.io.WinNTFileSystem.getBooleanAttributes (inFile.exists()) (~1 second) - StardardRoot.java (~1 second) Is there a reason DSpace would launch a check like this every ~20 seconds? Or could Tomcat have a reason to launch something to find out if a file exists? A contributor on Stack Overflow discovered that curated tasks could be run on a schedule -- is there a way to disprove a DSpace scheduled / periodic task is running? When I ran a test curated task it appeared in the dspace.log file but no updates to the logs have happened in the last hour and yet the periodic spikes are still occurring. (Stack Overflow <http://stackoverflow.com/questions/34138850/what-would-cause-tomcat-v8-to-cpu-spike-with-periodic-regularity)> was updated as well.) -- You received this message because you are subscribed to the Google Groups "DSpace Technical Support" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/dspace-tech. For more options, visit https://groups.google.com/d/optout.
