我正在使用Rails 5.1。我已经在Rails中设置了全局的memory_store缓存。这是在我的config/environments/development.rb文件中进行设置。
£ Enable/disable caching. By default caching is disabled.
if Rails.root.join('tmp/caching-dev.txt').exist?
config.action_controller.perform_caching = true
config.cache_store = :memory_store
config.public_file_server.headers = {
'Cache-Control' => 'public, max-age=172800'
}
else
config.action_controller.perform_caching = true
config.cache_store = :memory_store
end
这使我能够做一些像这样的事情：
Rails.cache.fetch(cache_key) do
msg_data
end
我的应用程序有两个部分，一个是web socket，另一个是controller。我希望在web socket中获取数据，并在controller中使用该数据。然而，我发现如果我使用puma启动Rails服务器（例如，在config/puma.rb文件中包含以下内容）...
threads_count = ENV.fetch("RAILS_MAX_THREADS") { 5 }.to_i
threads threads_count, threads_count
£ Specifies the `port` that Puma will listen on to receive requests, default is 3000.
£
port ENV.fetch("PORT") { 3000 }
£ Specifies the number of `workers` to boot in clustered mode.
£ Workers are forked webserver processes. If using threads and workers together
£ the concurrency of the application would be max `threads` * `workers`.
£ Workers do not work on JRuby or Windows (both of which do not support
£ processes).
£
workers ENV.fetch("WEB_CONCURRENCY") { 4 }
app_dir = File.expand_path("../..", __FILE__)
shared_dir = "£{app_dir}/shared"
£ Default to production
rails_env = ENV['RAILS_ENV'] || "production"
environment rails_env
£ Set up socket location
bind "unix://£{shared_dir}/sockets/puma.sock"
£ Logging
stdout_redirect "£{shared_dir}/log/puma.stdout.log", "£{shared_dir}/log/puma.stderr.log", true
£ Set master PID and state locations
pidfile "£{shared_dir}/pids/puma.pid"
state_path "£{shared_dir}/pids/puma.state"
activate_control_app
£ Use the `preload_app!` method when specifying a `workers` number.
£ This directive tells Puma to first boot the application and load code
£ before forking the application. This takes advantage of Copy On Write
£ process behavior so workers use less memory. If you use this option
£ you need to make sure to reconnect any threads in the `on_worker_boot`
£ block.
£
£ preload_app!
£ The code in the `on_worker_boot` will be called if you are using
£ clustered mode by specifying a number of `workers`. After each worker
£ process is booted this block will be run, if you are using `preload_app!`
£ option you will want to use this block to reconnect to any threads
£ or connections that may have been created at application boot, Ruby
£ cannot share connections between processes.
£
on_worker_boot do
require "active_record"
ActiveRecord::Base.connection.disconnect! rescue ActiveRecord::ConnectionNotEstablished
ActiveRecord::Base.establish_connection(YAML.load_file("£{app_dir}/config/database.yml")[rails_env])
end
£ Allow puma to be restarted by `rails restart` command.
plugin :tmp_restart
在内存缓存不再有效。换句话说，即使您将数据存储在内存中，当应用程序重新启动时，这些数据也会消失。
Rails.cache.fetch(cache_key)
这段代码总是返回空值。我希望拥有一个多线程的 Puma 环境（最终），以优雅地处理许多请求。但我也希望我的缓存能够正常工作。如何使它们同时协同工作呢？