Feature: Introduce "Effective Load" metric (power-normalized usage)

[airvzxf]

Description

This PR implements the “Effective Load” metric discussed in Issue #422.

The goal is to provide a more realistic representation of GPU usage by weighting the GPU Load against the current power consumption relative to the TDP.

Technical Implementation

1. Data Extraction (extract_gpuinfo.c)
I added a helper function calculate_effective_load that runs after the standard dynamic info refresh.

• Logic: Effective Load = GPU_Util_Rate * (Power_Draw / Power_Draw_Max)
• Safety: The calculation is strictly conditional. It only executes if power_draw, power_draw_max, and gpu_util_rate are valid and greater than zero. If the driver (e.g., some AMD/Intel implementations) does not provide Power_Draw_Max, the field remains unset/invalid.

2. Interface (interface.c)

• Added a new text field in the device header: Eff. XX%.
• This field is positioned after the power metrics.
• If the data is unavailable, it displays Eff. N/A.

3. Plotting & Options (interface_options.c, interface_setup_win.c)

• Added plot_effective_load_rate to the plotting enum.
• Users can now select “Effective load rate” in the Setup Menu (F2) to visualize this metric over time in the main graph.

Screenshots

Testing

I have tested this on my local machine.

• Scenario: High GPU load reported but low-power consumption -> Effective Load correctly shows a low percentage.
• Scenario: Stress test (high load + high power) -> Effective load converges with standard GPU load.

I look forward to your feedback.

[airvzxf]

I noticed a defect/oversight in this initial implementation.

Before I push the fix and polish the code, I wanted to confirm if the “effective load” concept is something you are interested in merging. If the feature aligns with your goals for nvtop, please let me know, and I will resolve the issue immediately.

Defect: shows RAM.

Release and stable version: shows GPU memory.

[airvzxf]

Update regarding the defect I mentioned:

Good news: I performed a clean fetch of master and confirmed that the issue is pre-existing and unrelated to my changes in this PR.

I tracked down the regression to commit d955f94 (specifically in extract_gpuinfo_nvidia.c), where it seems system RAM is being reported instead of GPU memory.

Specifically, the logic change here seems to be the culprit:

nvtop/src/extract_gpuinfo_nvidia.c

Lines 645 to 648 in 4bf5db2

	} else {
	// Memory query failed - likely unified memory GPU
	has_unified_memory = true;
	}

I will open a separate issue to track that bug so we can keep this PR focused on the “Effective Load” feature.

[airvzxf]

I added a follow-up commit to clamp the effective load value to 100%.

I realized that during transient power spikes or scenarios where power limits are raised (overclocking), the Current Power can slightly exceed the reported Max Power. This fix ensures the plotting logic stays within valid bounds to prevent visual glitches in the graph.

[Copilot]

Copilot encountered an error and was unable to review this pull request. You can try again by re-requesting a review.

[Syllo]

Thanks a lot for this, I think it's a really helpful metric to have