December 30, 2019 Runtime based caching by Alexander Vershilov Keywords:

Today I want to continue describing how we have made our services fast enough. In the contest service, one obvious bottleneck is the database. When many users send requests, we have to generate lots of connections and perform many queries. The obvious solution here is to introduce a caching mechanism. In this post, I’m going to describe some solutions available in the Haskell ecosystem and our solution, that is quite interesting.

Firstly we define options we need:

We need a caching mechanism that saves us from queries to the database.

A cache should be memory bounded, so our application does not consume all the memory.

Besides, we want to be able to set up sound strategies for the cache eviction, and but we will discuss that that before providing our solution.

Option one: use LRU-cache.

The simplest option is to take some LRU cache. This approach keeps memory bound by allowing only fixed amount of items in the cache. And it provides a strategy for increasing hit-rate by keeping least recently used items in the cache.

The best Haskell package for the LRU cache I’ve found so far is lrucaching. This package is based on the psqueues that provides the fastest immutable priority queues in the Haskell ecosystem. How the pseudo-code can look like:

<- atomicModifyIORef' ref $ \cache -> {-1-} resultatomicModifyIORef' ref\cache case lookup key cache of {- 2-} key cache Nothing -> (cache, Left key) (cache,key) Just (value, cache') -> (cache', Right value) (value, cache')(cache',value) case result of result Left key' -> do key' <- performQuery key' resultperformQuery key' $ \cache -> atomicModifyIORef' ref\cache (insert key value cache, ()) pure result result Just result -> pure result resultresult

Here we first check if the value is in the cache or it’s not. We use atomicModifyIORef' call that is a CAS operation that is quite fast but we may run several retries under contention. Then we perform a query and save the result of the computation in the cache if needed, or just return a cached result otherwise.

The solution is nice and simple. We use it in several places in the codebase. However, we have a problem with this solution. If many threads come for the same key, then all the requests do not find the key and execute a query to the database. So this approach does not save us from the first requests burst that is the most dangerous for our service. So we want to solve a problem of such bursts, we want to increase chances that if two requests come for the same key simultaneously, then only one request to the database is made.

The simplest but not affordable solution is to introduce a critical section, so only one request is run at a time:

$ \_ -> do withMVar lock\_ $ ... atomicallyModifyIORef ref

This solution is too coarse; we still want requests for the different thread to be run simultaneously. We can achieve that by keeping a lock in the cache. Still, if we go this way solution exceeds the complexity budget quite fast: you’ll need STM solution with explicit locking careful exception handing. You can try to implement that yourself.

The interesting thing is that the GHC runtime system already provides the tooling that is enough to build such cache without an explicit lock. When thunk that is evaluated all other threads accessing that thunk block on evaluation and automatically get a result once it’s evaluated. Now let’s check our solution.

Option two: Haskell runtime based solution.

Before describing the solution, let’s talk a bit more on the cache eviction. On the early stages of our system, we have decided that cached values may be updated, but it’s ok to keep value in the cache for a limited time. So LRU cache doesn’t work here, as naive variant does not provide such a guarantee: value may live in the cache forever. So instead, we keep the unlimited amount of values but remove values that are too old. We are using psqueues package still.

So the cache itself provides the following interface:

data Handle key result = Handle key result { requestOrInternal :: POSIXTime -- ^ current time -> key -- ^ key key -> (key -> IO result) -- ^ function to get the value (keyresult) -> IO result result , ... }

The meaning is the following: we provide current time, key, and a function that generates a value in case if the key is not found. And this function returns a result (or throws an exception). Handle provides us with a way to change the actual implementation without changing the interface and code that uses it, you may read more on that approach in the following posts 1, 2.

Now, to the actual implementation. Let’s introduce that line by line:

new :: IO ( Handle a b) a b) = do new <- newIORef PSQ.empty -- Create new priority queue. refnewIORef PSQ.empty pure $ Handle = \current_time key f -> mdo { requestOrInternal\current_time key fmdo ...

mdo - provides recursive do notation. It allows us to refer to the values that we will get in the future.

Now we need to read the cache, to see if there is a value there:

<- m_result atomicModifyIORef ref $ swap swap . PSQ.alter PSQ.alter case (\ Just (p, ~ v) (p,v) | p >= current_time ^-^ configLongestAge -> {- 1 -} current_timeconfigLongestAge ( Just v, Just (current_time, v)) v,(current_time, v)) _ -> ( Nothing , Just (tm, Lazy eresult)) {-2-} (tm,eresult)) ) key

We update a value in the key and get a result using the following rules:

{-1-} in case if there is a value, and it lived no more than maximum allowed age then we keep the value untouched and return us that value.

in case if there is a value, and it lived no more than maximum allowed age then we keep the value untouched and return us that value. {-2-} otherwise we return nothing from the cache and store the result of our future call in the cache (!).

So basically we have stored a result that we don’t even have at the moment, as we have not run the query still. It may sound mindblowing, but it’s perfectly fine in a lazy language.

Note lazy matching of the value ~v on the line {-1-} ; it means that we don’t try to inspect the value and return whatever is there. It seems that this protection is not required, but it’s better to be safe than sorry.

Another thing is that we wrap our result in a Lazy data structure:

data Lazy a = Lazy { getLazy :: a} a}

This way WHNF of the value doesn’t evaluate result itself, otherwise, we’d get a <loop> when storing result (as we don’t have the result yet, and our thread would need the result at hands to finish alter action).

Now we can analyze the result and perform query if needed (skipping some logging):

<- try $ maybe eresulttry {-1-} (f k) -> do (\r >>= \ case {-2-} evaluate (getLazy r) Left s -> throwIO s throwIO s Right x -> pure x ) m_result

We analyze the result, as you remember in a case if we have Nothing there we should perfom our request, and we do that on line {-1-} . We bind the result of our request to the result name (this is exactly the value we have already put in the cache). It keeps either exception value or the result. Otherwise, there is a result (or a thread working on generating that result). We need to force that (evaluate (getLazy r)) . In a case when the value is already evaluated, we get the result immediately. Otherwise, we block on evaluation, and the Haskell runtime handles it. We have 2 options afterwards, either the query results in an exception, then we rethrow it, or we get a result.

Now we need to do some cleanup, we do not want to keep exception result in the case, so we clean the cache in this case:

<- case eresult of resulteresult Left ( s:: SomeException ) -> do $ \v -> (PSQ.delete k v, ()) atomicModifyIORef' ref\v(PSQ.delete k v, ()) throwIO s Right x -> pure x

We must keep value with an exception in the cache first: this way all the threads that made the same request while our thread is performing request raise an exception.

The last step is to try to clean the oldest value. There may be better strategies for cleaning, but this strategy is straightforward and it works:

$ swap . PSQ.alterMin atomicModifyIORef' refswapPSQ.alterMin case (\ Nothing -> ((), Nothing ) ((), Just (kk, p, v) (kk, p, v) | p < tm ^-^ configLongestAge -> ((), Nothing ) tmconfigLongestAge((), | otherwise -> ((), Just (kk, p, v)) ((),(kk, p, v)) ) pure result result

This solution worked just fine for 1.5 years under heavy usage, and we have experienced 2 bugs there:

One found during early testing stage (it even didn’t hit repository branch): the requirement to use Lazy wrapper

wrapper Another one found after a year of usage in production when it exception happened in request f. Previously there we kept Lazy result in the cache, instead of Lazy (Either SomeException result) . As a result, in case of an exception in f, nobody can populate the value in the cache. And other threads wait forever on update. This unfortunate event has hit 2 users :(.

Please enable JavaScript to view the comments powered by Disqus.

Disqus