Hi All! Is there a way to cache dependencies in se...
# seed
a
Hi All! Is there a way to cache dependencies in seed? Havent timed it but anecdotally our seed deploys take longer than local deploys and cached dependencies seem like the most likely culprit
f
Hey @Alex Ketchum, is this a Node.js repo? SEED tries to cache the node modules automatically - https://seed.run/docs/caching-dependencies
Are you seeing a long yarn/npm install time?
a
it is node.js yes! yarn takes ~200 seconds on a recent service deploy, the deploy to cloudformation only takes 128 seconds. Also, why is serverless installed each time? thats another 25 seconds.
We love seed, but the build times are inconveniently long at the moment. I expect there is a lot of low hanging fruit that we can do to optimize, but I am not sure we know where to start. Do you have any resources for self directing our attempt to speed things up?
for example, a service just took 7 build min (6:33) to deploy, where as locally this would take less than half that time
f
Can you send me a link to the build on SEED?
(we work together not just jumping in randomly lol)
f
lol taking a look
looking at the logs, are you guys using Yarn 2 by any chance?
a
our yarnrc file in the project has the yarn path as yarn-3.0.1
f
Got it!
a
hey @Frank, any suggestions on what we could read up on to try and reduce these seed build times?
j
Also is there any chance the ability to ignore changes in certain files will be implemented anytime soon for SEED @Frank?
f
@Alex Ketchum any suggestions on what we could read up on to try and reduce these seed build times?
We did some research, and it seems for Yarn 2, we’d need to cache the
.yarn/cache
directory along with
node_mdoules
to make subsequent
yarn install
blazing fast. I will try to prioritize for this. Will keep you posted!
@Jacob Hayes yup, we are working on it!
j
Thanks Frank, really appreciate it!
@Frank any update on the above “caching
.yarn/cache
 directory along with 
node_mdoules
” to try to help speed up yarn installs?
It looks like we’re seeing some caching but it’s just a few packages:
Copy code
4 packages were already cached, 1971 had to be fetched
n
@Frank We are also facing the exact same problem. When is this fix coming out?