You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Yes. I have tried the latest release, but the bug still exist.
Try alternative boot mode
Yes. I have tried them, but the bug still exist.
BIOS Mode
Legacy BIOS Mode
Partition Style
MBR
Disk Capacity
32GB
Disk Manufacturer
Kingston
Image file checksum (if applicable)
None
Image file download link (if applicable)
No response
What happened?
Ever since I made a full hardware upgrade, Ventoy's menu became extremely slow to draw and moving through the different selections also became laggy. I have to press an arrow key a few times until Ventoy understands I want the cursor to move to another entry. I made a short video of what is happening with the menu:
With my old PC config which was 3 times slower in every aspect (including RAM and CPU), Ventoy was drawing the menu in a Flash.
I tried:
• Uninstall 1.0.99 and then install it again (after formatting the USB stick).
• Uninstall 1.0.99 and install a few older versions including 1.0.98 one after the other but nothing changed, so I left it at 1.0.98 atm.
• Adjusting the motherboard's settings regarding PCIE1 slot, CPU and RAM because I thought the slowness might be caused by mismatching "auto" settings (it wouldn't be the first time for "auto" to suck in AsRock motherboards). After setting it up with proper settings the PC became a lot faster but Ventoy remained slow and laggy.
At this point I'm out of ideas what else to try.
Edit:
I found out WHY it has become slower: because Ventoy uses the efficiency cores, not the performance cores of the CPU (i7-12700F).
I found a workaround to use the programs I was booting from Ventoy (GParted & Clonezilla) but in any case you'll have to write some code to force Ventoy ignore the presense of efficiency cores and use only performance cores.
The text was updated successfully, but these errors were encountered:
rado84-github
changed the title
[issue]: Ventoy menu became a lot slower after a complete hardware upgrade
[issue]: Ventoy using the wrong cores in i7-12700
Nov 1, 2024
Official FAQ
Ventoy Version
1.0.99, 1.0.98
What about latest release
Yes. I have tried the latest release, but the bug still exist.
Try alternative boot mode
Yes. I have tried them, but the bug still exist.
BIOS Mode
Legacy BIOS Mode
Partition Style
MBR
Disk Capacity
32GB
Disk Manufacturer
Kingston
Image file checksum (if applicable)
None
Image file download link (if applicable)
No response
What happened?
Ever since I made a full hardware upgrade, Ventoy's menu became extremely slow to draw and moving through the different selections also became laggy. I have to press an arrow key a few times until Ventoy understands I want the cursor to move to another entry. I made a short video of what is happening with the menu:
https://imgur.com/a/ZMomSAk
With my old PC config which was 3 times slower in every aspect (including RAM and CPU), Ventoy was drawing the menu in a Flash.
I tried:
• Uninstall 1.0.99 and then install it again (after formatting the USB stick).
• Uninstall 1.0.99 and install a few older versions including 1.0.98 one after the other but nothing changed, so I left it at 1.0.98 atm.
• Adjusting the motherboard's settings regarding PCIE1 slot, CPU and RAM because I thought the slowness might be caused by mismatching "auto" settings (it wouldn't be the first time for "auto" to suck in AsRock motherboards). After setting it up with proper settings the PC became a lot faster but Ventoy remained slow and laggy.
At this point I'm out of ideas what else to try.
Edit:
I found out WHY it has become slower: because Ventoy uses the efficiency cores, not the performance cores of the CPU (i7-12700F).
I found a workaround to use the programs I was booting from Ventoy (GParted & Clonezilla) but in any case you'll have to write some code to force Ventoy ignore the presense of efficiency cores and use only performance cores.
The text was updated successfully, but these errors were encountered: