For years, people have been using jemalloc with ruby. There were various benchmarks and discussions. Legend had it that Jemalloc 5 didn't work as well as Jemalloc 3.
Then, one day, hope appeared on the horizon. @wjordan offered a config for Jemalloc 5.
FROM ruby:3.1.2-bullseye
RUN apt-get update ; \
| # A script to migrate Sidekiq's redis to a new server. | |
| # This obviously can work for any redis, but I only handled | |
| # data types that Sidekiq uses. | |
| require 'redis' | |
| old_redis = Redis.new url: 'redis://old-redis:6379' | |
| new_redis = Redis.new url: 'redis://new-redis:6379' | |
| unknowns = [] |
Add the following to application.rb:
$icallbacks = []
$icallbacks.define_singleton_method(:print) do
puts sort_by { |(a, b)| -b }.map { |(a, b)| "#{b}\t\t#{a}" }.join("\n")
end
ActiveSupport::Notifications.subscribe("load_config_initializer.railties") do |event|
$icallbacks << [event.payload[:initializer], event.duration]
Consistency in naming makes reading and memory retrieval much, much easier. Conversely, changing rules and mixing conventions are very confusing and significantly increase cognitive load. Follow language, company, and project conventions for names, even if you don't like them.
After factory resetting the maching you will need to do the following things to bootstrap it with Ansible.
chsh -s /bin/bash (optional)xcode-select --installexport PATH="$HOME/Library/Python/3.8/bin:$PATH"This small module sets up VCR in a way that makes using VCR in Minitest a breeze.
You can wrap specific parts of your test in a with_vcr block that will automatically
create and name a cassette and directory based on the test and class name, and handles nested names.
It works great both from inside Rails, and not.
The example test file in this gist stores its results to test/vcr/Search_GoogleTest/test_search.yml.
| # Stick this in your home directory and point your Global Git config at it by running: | |
| # | |
| # $ git config --global core.attributesfile ~/.gitattributes | |
| # | |
| # See https://tekin.co.uk/2020/10/better-git-diff-output-for-ruby-python-elixir-and-more for more details | |
| *.c diff=cpp | |
| *.h diff=cpp | |
| *.c++ diff=cpp | |
| *.h++ diff=cpp |
| #!/bin/bash | |
| # | |
| # Self-contained command line processing in bash that supports the | |
| # minimal, lowest common denominator compatibility of flag parsing. | |
| # -u: undefined variables is an error | |
| # -e: exit shell on error | |
| set -eu | |
| function usage() { |
Added the document to Medium and expanded it a bit with more configuration examples:
After a lot of headace and sturggle i went back to what i trust. no more Laravelt Valet or Valet-plus or any other wrappers and workarounds. Sure a few things like enabling and disabling Xdebug is a tad bit more work. but its matter of seconds.
| #!/bin/bash | |
| source ~/.bash_profile | |
| if hash sdk 2>/dev/null; then | |
| sdk current | |
| echo "Gradle cache:" | |
| pushd ~/.gradle/caches && tree | grep '.jar' | grep -v 'sources' | rev | cut -d' ' -f1 | rev | sed 's/[-_][0-9].*//' | sort| uniq | |
| popd | |
| fi | |
| if hash python2 2>/dev/null; then |
