New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Investigate why Vite is too slow #3855
Comments
I build the assets on my side. It's taking very less time compared to
OS : Ubuntu 20.04 LTS |
@tanmoysrt That could be because of the CPU cores and RAM availability in your machine |
Can you share the specs of the system , then I can try to reproduce the result and can try to find solution |
|
@tachyons @tanmoysrt how many times will we need to build these assets? |
@tanmoysrt 4GB ram single core ec2 instance @smritigarg Once for each deployment |
Thanks , will check that |
What is its os and version ? |
Ubuntu 20.04 |
I have tested this in EC2 with various configuration.
Little Optimization can be -
import { defineConfig } from 'vite'
import RubyPlugin from 'vite-plugin-ruby'
export default defineConfig({
build : {
sourcemap: false
},
plugins: [
RubyPlugin(),
],
}) @tachyons can we offload the task from the server? |
Yes, this step will be removed from server once the containarization is completed, still the speed of vite is significantly slower than esbuild based configuration. 10 seconds to 6 minutes is too much |
Yes the time is so high, and with lower resources it grows exponentially. With 300 mb ram & 30% VCPU it takes a round 35 minute to building. I am searching if this resource issue of vite can be solved somehow |
The text was updated successfully, but these errors were encountered: