tripplehelix, (edited )
@tripplehelix@fosstodon.org avatar

/ builds seem to run very slow on my AMD system. They didn't take anywhere near as long on my old Intel system. Looking at btop it only seems to use one thread during , am I missing something?

(Intel 11th Gen I7 & AMD Ryzen 7 7840U)

mo8it,
@mo8it@fosstodon.org avatar

@tripplehelix Could you please provide the output of the command rustc --print cfg | grep target?

tripplehelix,
@tripplehelix@fosstodon.org avatar
mo8it,
@mo8it@fosstodon.org avatar

@tripplehelix Then, could you please run this tiny Rust program and provide its output?

fn main() {  
 println!("{:?}", std::thread::available_parallelism());  
}  
tripplehelix,
@tripplehelix@fosstodon.org avatar

---- deleted ---

tripplehelix, (edited )
@tripplehelix@fosstodon.org avatar

@mo8it

~► ./rust  
Ok(16)  
tripplehelix,
@tripplehelix@fosstodon.org avatar

@mo8it Maybe the issue isn't that. Compiling barely uses any CPU and only ever hits one core hard. Maybe it's being limited by something.

mo8it,
@mo8it@fosstodon.org avatar

@tripplehelix Looks good. Weird.

In Gnome, there is a setting for energy consumption for AMD CPUs. Make sure that you have the performance mode and not power saving.

tripplehelix,
@tripplehelix@fosstodon.org avatar

@mo8it My computer is running in 'Desktop' mode was in 'Balanced' via tuned. But then I used balanced mode on the intel machine.

I run XFCE. Think this is going to be one of those issues that just surprises me and suddenly works properly.

tripplehelix,
@tripplehelix@fosstodon.org avatar

@mo8it OK this seems to be a much more widespread issue, as even clamscan uses only 6% CPU.

Thanks for the help though!

dcz,
@dcz@fosstodon.org avatar

@tripplehelix Compare Rust version and exact crate contents. Operating system shouldn't matter but can't be eliminated.

tripplehelix,
@tripplehelix@fosstodon.org avatar

@dcz I've tried the stable rustup tool kit and nightly, both the same issue, currently have rustc 1.79.0-nightly.

The slow compile happens most glaringly with the eza and spotify_player crates, but also with alacritty.

Using Debian Sid, but I was also on Sid on Intel. My first thought was that it might be some issue with the t_64 transition. Maybe some packages are just struggling.

dcz,
@dcz@fosstodon.org avatar

@tripplehelix I think you should dig more into the versions: it's not clear from what you wrote that you were actually using the same versions between builds - neither of rustc nor of the crates.

  • All
  • Subscribed
  • Moderated
  • Favorites
  • rust
  • DreamBathrooms
  • magazineikmin
  • everett
  • InstantRegret
  • rosin
  • Youngstown
  • slotface
  • love
  • khanakhh
  • kavyap
  • tacticalgear
  • GTA5RPClips
  • thenastyranch
  • modclub
  • anitta
  • mdbf
  • tester
  • Durango
  • ethstaker
  • osvaldo12
  • cubers
  • ngwrru68w68
  • provamag3
  • normalnudes
  • Leos
  • cisconetworking
  • megavids
  • JUstTest
  • All magazines