Thread pools on the JVM should usually be divided into the following three categories:
- CPU-bound
- Blocking IO
- Non-blocking IO polling
Each of these categories has a different optimal configuration and usage pattern.
| diff --git a/builddefs/common_features.mk b/builddefs/common_features.mk | |
| index 18f8b0bbfc..4ef3e230e4 100644 | |
| --- a/builddefs/common_features.mk | |
| +++ b/builddefs/common_features.mk | |
| @@ -878,6 +878,10 @@ ifeq ($(strip $(JOYSTICK_ENABLE)), yes) | |
| endif | |
| endif | |
| +ifeq ($(strip $(APPLE_FN_ENABLE)), yes) | |
| + OPT_DEFS += -DAPPLE_FN_ENABLE |
| function fish_greeting | |
| echo ' '(set_color F00)'___ | |
| ___======____='(set_color FF7F00)'-'(set_color FF0)'-'(set_color FF7F00)'-='(set_color F00)') | |
| /T \_'(set_color FF0)'--='(set_color FF7F00)'=='(set_color F00)') '(set_color red)(whoami)'@'(hostname)' | |
| [ \ '(set_color FF7F00)'('(set_color FF0)'0'(set_color FF7F00)') '(set_color F00)'\~ \_'(set_color FF0)'-='(set_color FF7F00)'='(set_color F00)')'(set_color yellow)' Uptime:'(set_color white)(uptime | sed 's/.*up \([^,]*\), .*/\1/')(set_color red)' | |
| \ / )J'(set_color FF7F00)'~~ \\'(set_color FF0)'-='(set_color F00)') Theme: '(set_color white)(echo $fisher_active_prompt)(set_color red)' | |
| \\\\___/ )JJ'(set_color FF7F00)'~'(set_color FF0)'~~ '(set_color F00)'\) '(set_color yellow)'Version: '(set_color white)(echo $FISH_VERSION)(set_color red)' | |
| \_____/JJJ'(set_color FF7F00)'~~'(set_color FF0)'~~ '(set_color F00)'\\ Date: '(set_color white)(date)(set_color red)' | |
| '(set_color FF7F00)'/ '(set_color |
| <?xml version="1.0" encoding="UTF-8"?> | |
| <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd"> | |
| <plist version="1.0"> | |
| <dict> | |
| <key>EnvironmentVariables</key> | |
| <dict> | |
| <key>PATH</key> | |
| <string>/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin</string> | |
| </dict> | |
| <key>Label</key> |
| def cachingWithTTL[T, M[_]](keyParts: Any*)(value: => M[(T, Duration)]) | |
| (implicit cache: Cache[T], mode: Mode[M], flags: Flags): M[T] = { | |
| import mode._ | |
| M.flatMap(get(keyParts:_*)) { | |
| case Some(found) => M.pure(found) | |
| case None => | |
| M.flatMap(value) { | |
| case (v, ttl) => | |
| M.map(put(keyParts:_*)(v, Some(ttl)))(_ => v) | |
| } |
| diff --git a/$line3/$read$$iw$$iw$.class.asm b/$line3/$read$$iw$$iw$.class.asm | |
| index af096b7..8c7fc90 100644 | |
| --- a/$line3/$read$$iw$$iw$.class.asm | |
| +++ b/$line3/$read$$iw$$iw$.class.asm | |
| @@ -1,30 +1,23 @@ | |
| // class version 52.0 (52) | |
| -// access flags 0x21 | |
| -public class $line3/$read$$iw$$iw$ { | |
| +// access flags 0x31 | |
| +public final class $line3/$read$$iw$$iw$ { |
| #!/bin/bash | |
| # Minimum TODOs on a per job basis: | |
| # 1. define name, application jar path, main class, queue and log4j-yarn.properties path | |
| # 2. remove properties not applicable to your Spark version (Spark 1.x vs. Spark 2.x) | |
| # 3. tweak num_executors, executor_memory (+ overhead), and backpressure settings | |
| # the two most important settings: | |
| num_executors=6 | |
| executor_memory=3g |
I've had many people ask me questions about OpenTracing, often in relation to OpenZipkin. I've seen assertions about how it is vendor neutral and is the lock-in cure. This post is not a sanctioned, polished or otherwise muted view, rather what I personally think about what it is and is not, and what it helps and does not help with. Scroll to the very end if this is too long. Feel free to add a comment if I made any factual mistakes or you just want to add a comment.
OpenTracing is documentation and library interfaces for distributed tracing instrumentation. To be "OpenTracing" requires bundling its interfaces in your work, so that others can use it to time distributed operations with the same library.
OpenTracing interfaces are targeted to authors of instrumentation libraries, and those who want to collaborate with traces created by them. Ex something started a trace somewhere and I add a notable event to that trace. Structure logging was recently added to O
The count of contributions (summary of Pull Requests, opened issues and commits) to public repos at GitHub.com from Wed, 29 Jul 2015 01:52:41 GMT till Fri, 29 Jul 2016 01:52:41 GMT.
Only first 1000 GitHub users according to the count of followers are taken. This is because of limitations of GitHub search. Sorting algo in pseudocode:
githubUsers
.filter(user => user.followers > 6)