#Astro build with 130 blogs

45 messages · Page 1 of 1 (latest)

thorn kayak
#

Hi, I have one problem with blogs in my repo.

So i have about 130 blogs and each blog has its own heroImage and I have problem building my site because it takes about 20 minutes and fails because of time limit... Here are 2 pictures how i display my blogs and I tried everything without SSR too.

My question is what can i do to speed up building of all those images. Thanks.

I am using Astro Image component for displaying images

barren ginkgo
#

i am unable to run

thorn kayak
#

please write you new post and delete it from here because its not the same problem

gritty ether
# barren ginkgo i am unable to run

Hey @barren ginkgo You probably want to open a separate thread in #1019713903481081876 as it does not look like your issue is related to this post and I would hate for you to not get the help you need 😦

gritty ether
#

@paper hazel The support thread referenced in #general message

paper hazel
#

Ok so if you’re using <Image /> this will handle caching for you @thorn kayak

#

can you show the errors you’re getting during build

thorn kayak
#

Its just that it takes too long to build

paper hazel
#

Are you using Astro compress integration ?

#

If so try turning that off and the rebuild

thorn kayak
#

yes i have that

paper hazel
#

Try without that

thorn kayak
#

whatt?? so it build in 10 seconds?

paper hazel
#

Yes that integration is extremely aggressive version of sharp

#

And it’s going through all the versions of your images

#

I don’t know why it’s timing out though

#

If you want to keep using it I would open an issue on its repo

#

But you don’t need it at all

thorn kayak
#

so is it bad that i have withouth compress or its whatever?

#

oh so its not needed

paper hazel
#

No compress is not needed at all

thorn kayak
#

oh okay

#

will push to repo and will let you know if preview builds

paper hazel
#

you already have minified html css and js files as well as images

thorn kayak
#

oh okay thanks for letting me know

paper hazel
#

I used to use that too and gave up on it since it caused me weird issues in past

thorn kayak
#

oh yea, it build my site in preview

#

its working thanks

paper hazel
#

Anytime 🎉

thorn kayak
#

i wasted 10 hours

#

on that bug

#

and it was just that

#

😭

paper hazel
#

Relatable haha sorry to hear that

thorn kayak
#

no problem

gritty ether
#

Dang sick work Oliver, I also learned something houston_fingerguns

#

Also

woven templeBOT
#
If your issue is resolved, please help by doing the following two steps:
  1. From the ellipses (3-dot menu) in the top-right corner of the post (not the first message), edit the tags to include the Solved tag.
  2. From the same ellipses, select Close Post.
    Your post will still be available to search and can be re-opened simply by replying in it. Closing a post moves it down with older posts, so we can more easily focus on issues that still need to be resovled.
    Thank you for your help!
radiant crown
#

@paper hazel @thorn kayak Hey I'm looking into this too right now. The reason I started going for playform/compress myself is that without it, all my code comments seem to be left in the deployed code, which is undesired.

In particular, simply enabling the HTML minification shows ~10% file size reduction for me. CSS compression doesn't seem like it works. JS compression is only like 0.5%.

So for blaz, you can likely adjust the compress integration settings like below to only have HTML minification.

compress({
      HTML: true,
      JavaScript: false,
      CSS: false,
      Image: false, // astro:assets handles this. Enabling this can dramatically increase build times
      SVG: false, // astro-icon handles this
    }),