sezaru
I was having a discussion with my team in my daily job yesterday and we talked a little bit about how Ash improved our productivity, etc. One negative point that was brought up was that we feel that our project take a lot of time to compile some of our resources (some of them take more than 30 seconds).
That made me wonder if there are some best practices and tips to make the resources as lightweight as possible.
One thing that I think slow down compilations (it is a guess, I didn’t test it out to confirm it or not), is adding has_many to resources even if we don’t actually use the relationship anywhere (for example: An User can have one Role, so we add a belongs_to to it, but then, the Role can have many users, so we add a has_many to it event though we never actually access the users from the Role resource).
So, is there some best practices, and tips and tricks to improve resource compilations?
Where Next?
Trending in Questions
Other Trending Topics
Latest Ash Threads
Latest on Elixir Forum
Sponsor Spotlight
Deploy Phoenix to your own VPS with PaaS ease: push-to-deploy, zero downtime, auto SSL, managed Postgres. 14-day free trial at potions.io
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #library
- #deployment
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #elixirconf
- #channels
- #exunit
- #discussion
- #code-sync
- #podcasts
- #javascript
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ai
- #ecto-query
- #elixirconf-us
- #blog-post
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #elixirconf-eu
- #api
- #forms
- #metaprogramming
- #hex
Our Sponsors
Build Elixir applications with speed and confidence.
Supporting innovation across the BEAM ecosystem.
We build reliable cloud platforms for business-critical systems.
Catch errors, track performance, monitor hosts and more.
Elixir, Erlang & BEAM conferences from Code Sync - join us in 2026!
Master modern tools, write cleaner code, and tackle real-world challenges.
Producing high quality Elixir screencasts since 2017.
The deployment platform built for Elixir: PaaS ease, VPS control.
The team behind Membrane, Popcorn, LiveDebugger. Available for hire.
Courses that'll move you from confusion to "Aha, now I get it!"
Showing Posts 1 to 9- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
sodapopcan
I have no idea if this affects compilation time but I’m a big advocate of not doing this. This is really no different than having “just in case” code/unused public functions. It can also lead to things like people preloading out of convenience when they shouldn’t be.
Schultzer
Lots of people think premature optimization is just about performance, but most of the time it falls in this category, building for a future that never will happen. It’s as destructive as early abstraction. Dead code has no place in your codebase, regardless of what the future holds.
zachdaniel
The biggest thing you can do here is to remove as many anonymous functions from your resources as possible and extract them into module changes/preparations etc.
sezaru
Actually, none of my changes/preparations uses anonymous functions, they are already all inside modules.
Do breaking the resource into fragments help in any way?
zachdaniel
I’ve heard that it can yes but I haven’t confirmed it personally.
nocsi
I had this same sort of problem and came up with ash_profiler | Hex
There’s an incredible amount of solving that goes on when you don’t go out of your way to break up resources
frankdugan3
That is really cool. I have an ERP in Ash that will definitely benefit from it. Seems like your Git repo is either private or wrong URL?
sezaru
This is amazing, I will try it out ASAP! Btw, seems like the github repo doesn’t exist.
nocsi
Sorry about that, was moving a bunch of projects into a new org so i could publish:
https://github.com/zpc-sh/ash_profiler
There you go. This ones for the devs that have over 30 attributes in an Ash Resource