WSSCode Blog

Pathom Updates 05, Speed check!

December 23, 2020

Hello everyone! Time for another round of updates! Before I start, I like to mention and thank Cognitect and Nubank for sponsoring my work. I feel honored to be a participant on their initiative, if you didn’t hear about it check this post from Rich Hickey.

Datafy Smart Maps

To start this update, Smart Maps now support Datafy and Navigation protocols!

This means that if you use a tool like Reveal or REBL you can lazily navigate the Smart Map possibilities!

Here you can see a demo exploring data on Reveal:

Now in REBL:


Back in September when I announced Pathom 3, I demonstrated a few benchmarks to show a rewrite’s potential. Now after a few months, the runner got: Placeholders, Unions, Parameters, Resolver Cache, Error handling, Batching, Execution analysis, and Mutations.

With all these new features, I think it’s an excellent time to take new measurements.

For the benchmarks I’ll use the following resolvers:

(defn slow-param-transform [config]
  (update config ::pco/resolve
    (fn [resolve]
      (fn [env input]
        (when-let [delay (-> (pco/params env) :delay)]
          (time/sleep-ms delay))
        (resolve env input)))))

(defn items-resolver [count]
  (let [kw (keyword (str "items-" count))]
    (pco/resolver (symbol (str "items-" count))
      {::pco/output [{kw [:id]}]
       ::pco/cache? false}
      (fn [{:keys [n]} _]
        {kw (mapv (fn [_] (hash-map :id (vswap! n inc))) (range count))}))))

(defn gen-resolvers [attr]
  (let [attr-s (name attr)]
    [(pco/resolver (symbol attr-s)
       {::pco/input     [:id]
        ::pco/output    [attr]
        ::pco/transform slow-param-transform}
       (fn [_ {:keys [id]}] {attr (* 10 id)}))

     (let [batch-attr (keyword (str attr-s "-batch"))]
       (pco/resolver (symbol (str attr-s "-batch"))
         {::pco/input     [:id]
          ::pco/output    [batch-attr]
          ::pco/batch?    true
          ::pco/transform slow-param-transform}
         (fn [_ ids]
           (mapv #(hash-map batch-attr (* 10 (:id %))) ids))))]))

(def env-indexes
    [(items-resolver 1)
     (items-resolver 10)
     (items-resolver 100)
     (items-resolver 1000)
     (items-resolver 10000)
     (gen-resolvers :x)
     (gen-resolvers :y)

     ; complex route
     (pbir/constantly-resolver :a 1)
     (pbir/single-attr-resolver :g :b inc)
     (pbir/constantly-resolver :c 2)
     (pbir/constantly-resolver :e 1)
     (update (pbir/constantly-resolver :e 3) :config assoc ::pco/op-name 'e1)
     (pbir/single-attr-resolver :e :f inc)
     (update (pbir/constantly-resolver :g 4) :config assoc ::pco/input [:c :f])
     (update (pbir/constantly-resolver :h 5) :config assoc ::pco/input [:a :b])]))

(defn base-env []
  (assoc env-indexes :n (volatile! 0)))

Single read

As I did last time, the first benchmark measures the time to do the minimal work to get some result of Pathom. It’s a query with a single attribute, which requires a single resolver call to realize.

Pathom 3 Cached Plan0.007ms0.000x
Pathom 30.035ms3.810x
Pathom 3 Async PromesaNaNmsx
Pathom 3 Core AsyncNaNmsx
Pathom 2 Serial0.058ms6.878x
Pathom 2 Async0.102ms12.833x
Pathom 2 Parallel0.144ms18.509x

Before moving on, let’s understand what the bars represent, from left to right:

  • p3-serial-cp: Pathom 3 serial parser, using a persistent plan cache. This means that the planning part of the operation is already pre-cached. It’s common for API’s to make the same queries over and over, this provides the opportunity to cache this step, and you may expect a high cache hit rate on this plan cache. They are based on the query and the available data.
  • p3-serial: Pathom 3 serial, without any pre-cache. Keep in mind that even if there is no pre-cache, Pathom will make a request level plan cache anyway. When there is a collection in the process, the plan is cached and re-utilized between the collection items.
  • p2-serial: Pathom 2 using the serial parser and reader2.
  • p2-async: Pathom 2 using the async parser and async-reader2.
  • p2-parallel: Pathom 2 using the parallel parser and parallel-reader.

Complex read

This example demonstrates a case where a single attribute requires a complex chain of resolvers to get fulfilled.

Pathom 3 Cached Plan0.042ms0.000x
Pathom 30.213ms4.105x
Pathom 3 Async PromesaNaNmsx
Pathom 3 Core AsyncNaNmsx
Pathom 2 Serial0.535ms11.848x
Pathom 2 Async1.056ms24.370x
Pathom 2 Parallel1.636ms38.285x

In this example, we can see the cache plan was even more effective, which makes sense given this requires the generation of many nodes while previous was a plan with a single node.

Here is what the process of :h looks like in this example:

Complex Graph


If you are not familiar with how Pathom 3 planing works and like to know more about the nodes generation check this documentation page.

Sequence of 1000 items

In this example, we will look at how long it takes for Pathom to process a collection with 1000 items in it, a simple resolver call on each.

[{:items-1000 [:x]}]
Pathom 3 Cached Plan12.584ms0.064x
Pathom 311.823ms0.000x
Pathom 3 Async PromesaNaNmsx
Pathom 3 Core AsyncNaNmsx
Pathom 2 Serial108.639ms8.189x
Pathom 2 Async226.384ms18.147x
Pathom 2 Parallel81.870ms5.924x

In this, we can see that Pathom 3 gets about eight times faster for raw sequence processing when compare to Pathom 2 serial.

Sequence of 1000 items in batch

Sample as the previous, but now with batched value processing.

[{:items-1000 [:x-batch]}]
Pathom 3 Cached Plan16.172ms0.061x
Pathom 315.241ms0.000x
Pathom 3 Async PromesaNaNmsx
Pathom 3 Core AsyncNaNmsx
Pathom 2 Serial113.813ms6.468x
Pathom 2 Async223.306ms13.652x
Pathom 2 Parallel57.038ms2.742x

Same similar gains in batching.

Nesting 10 > 10 > 10

Testing nesting, 3 levels down, 10 items per level.

Pathom 3 Cached Plan17.720ms0.027x
Pathom 317.258ms0.000x
Pathom 3 Async PromesaNaNmsx
Pathom 3 Core AsyncNaNmsx
Pathom 2 Serial129.452ms6.501x
Pathom 2 Async282.742ms15.383x
Pathom 2 Parallel106.562ms5.175x

Nesting 100 > 10, batch head

Nesting with batching, the batch occurring at the top.

Pathom 3 Cached Plan13.949ms0.000x
Pathom 314.493ms0.039x
Pathom 3 Async PromesaNaNmsx
Pathom 3 Core AsyncNaNmsx
Pathom 2 Serial126.786ms8.090x
Pathom 2 Async260.164ms17.652x
Pathom 2 Parallel112.960ms7.098x

Nesting 100 > 10, batch tail

Nesting with batching, the batch occurring at tail items.

Pathom 3 Cached Plan17.702ms0.000x
Pathom 318.023ms0.018x
Pathom 3 Async PromesaNaNmsx
Pathom 3 Core AsyncNaNmsx
Pathom 2 Serial133.504ms6.542x
Pathom 2 Async268.601ms14.174x
Pathom 2 Parallel53.008ms1.995x

Sequence of 100 items, batch with 200ms delay

  [(:x-batch {:delay 200})]}]
Pathom 3 Cached Plan205.625ms0.000x
Pathom 3205.644ms0.000x
Pathom 3 Async PromesaNaNmsx
Pathom 3 Core AsyncNaNmsx
Pathom 2 Serial220.460ms0.072x
Pathom 2 Async237.340ms0.154x
Pathom 2 Parallel212.722ms0.035x

This is a good example of how that when some resolvers are costly, the noticeable overhead gets reduced.

Nesting 10 > 10, batch with 20ms delay

    [(:x-batch {:delay 20})]}]}]
Pathom 3 Cached Plan25.972ms0.009x
Pathom 325.729ms0.000x
Pathom 3 Async PromesaNaNmsx
Pathom 3 Core AsyncNaNmsx
Pathom 2 Serial258.815ms9.059x
Pathom 2 Async281.882ms9.956x
Pathom 2 Parallel77.157ms1.999x

Continuous benchmarking

This time I made those benchmarks so that it will be easier to keep running them over time (they may go to a pipeline soon). I hope with this, we can avoid performance surprises due to the changes to come. It’s also a platform for trying out features and seeing if they cause impact the Pathom speed. This is just the beginning of Pathom benchmarking!

Plugins & Error handling

I was a bit concerned to add plugins before having these benchmarks, now that I can test out how the plugins architecture will affect performance I feel more comfortable starting it, which is the next thing on Pathom 3!

Error handling is related to plugins too, I’ve been silent working on it for some time, and I see that to complete the error handling story, I need plugins first. I’ll be writing more about those soon.

That’s what I have for today. Happy holidays everyone!

Support my work

I'm currently an independent developer and I spent quite a lot of my personal time doing open-source work. If my work is valuable for you or your company, please consider supporting my work though Patreon, this way you can help me have more available time to keep doing this work. Thanks!

Current supporters

And here I like to give a thanks to my current supporters: