If you're a git user, instead of increasing the numebr of threads, you might consider revisiting your polling definition. I was polling git once a minute from multiple jobs until I discovered the "Git polling must die" blog posting from Kohsuke.
I don't see it on my Jenkins instance that has more than 10 jobs defined, but there is an entry "SCM Polling" whose help text says "If you use SCM polling to trigger a new build for a large number of projects, you may want to limit the number of concurrent polling activities to avoid overloading the server. Setting a positive number sets the upper bound to the number of concurrent polling. Leaving the field empty will make it unbounded"
Mark Waite