This shows the execution order given JavaScript's Call Stack, Event Loop, and any asynchronous APIs provided in the JS execution environment (in this example; Web APIs in a Browser environment)
Given the code
Sparked from this twitter conversation when talking about doing fast async rendering of declarative UIs in Preact
These examples show how it's possible to starve the main event loop with microtasks (because the microtask queue is emptied at the end of every item in the event loop queue). Note that these are contrived examples, but can be reflective of situations where Promises are incorrectly expected to yield to the event loop "because they're async".
setTimeout-only.js
is there to form a baselineDownloads
directoryConsolas.ttf
fileInstall font
buttonAuthor: Chris Lattner
I came across HikariCP
and I was amazed by the benchmarks and I wanted to try it instead of my default choice C3P0
and to my surprise I struggled to get the configurations
right probably because the configurations differ based on what combination of tech stack you are using.
I have setup Spring Boot
project with JPA, Web, Security
starters (Using [Spring Initializer][1]) to use PostgreSQL
as a database with HikariCP
as connection pooling.
I have used Gradle
as build tool and I would like to share what worked for me for the following assumptions:
This gist is related to SO post https://stackoverflow.com/questions/26490967/how-do-i-configure-hikaricp-in-my-spring-boot-app-in-my-application-properties-f
0⃣ 0, keycap, zero | |
1⃣ 1, number, one | |
🕜 1, 30, clock, time, one, thirty, 1:30, one-thirty | |
🕐 1, clock, time, one, 00, o’clock, 1:00, one o’clock | |
2⃣ 2, number, two | |
🕝 2, 30, clock, time, two, thirty, 2:30, two-thirty | |
🕑 2, clock, time, two, 00, o’clock, 2:00, two o’clock | |
3⃣ 3, keycap, three | |
🕞 3, 30, three, clock, time, thirty, 3:30, three-thirty | |
🕒 3, three, clock, time, 00, o’clock, 3:00, three o’clock |
name: Security audit | |
on: | |
schedule: | |
- cron: '0 0 * * *' | |
push: | |
paths: | |
- '**/Cargo.toml' | |
- '**/Cargo.lock' | |
jobs: | |
security_audit: |
# THIS LINUX SETUP SCRIPT HAS MORPHED INTO A WHOLE PROJECT: HTTPS://OMAKUB.ORG | |
# PLEASE CHECKOUT THAT PROJECT INSTEAD OF THIS OUTDATED SETUP SCRIPT. | |
# | |
# | |
# Libraries and infrastructure | |
sudo apt update -y | |
sudo apt install -y \ | |
docker.io docker-buildx \ | |
build-essential pkg-config autoconf bison rustc cargo clang \ |
import java.time.Duration; | |
import java.util.List; | |
import java.util.concurrent.locks.ReentrantLock; | |
import java.util.stream.IntStream; | |
import java.util.stream.Stream; | |
/** | |
* Demonstrate potential for deadlock on a {@link ReentrantLock} when there is both a synchronized and | |
* non-synchronized path to that lock, which can allow a virtual thread to hold the lock, but | |
* other pinned waiters to consume all the available workers. |