Jump to content
Sign in to follow this  
RSMAN96

Can't understand CPU usage

Recommended Posts

I have read threads here including TRIlez's and have trawled google and tried various things but I just don't know what is wrong. My CPU usage is all over the place when botting. It can go from 5% to 30 and back down in an instant. Not only that but I can only max out on 7-8 bots and a computer of my caliber should be capable of more. Yes I have used low cpu mode and put everything on the lowest possible setting. I have even used different botting clients and used different scripts to no avail. I am hoping someone may have a solution for this.

Specs:

16gb ram

I7 intel quad core 6700k

Share this post


Link to post
Share on other sites
18 minutes ago, RSMAN96 said:

I have read threads here including TRIlez's and have trawled google and tried various things but I just don't know what is wrong. My CPU usage is all over the place when botting. It can go from 5% to 30 and back down in an instant. Not only that but I can only max out on 7-8 bots and a computer of my caliber should be capable of more. Yes I have used low cpu mode and put everything on the lowest possible setting. I have even used different botting clients and used different scripts to no avail. I am hoping someone may have a solution for this.

Specs:

16gb ram

I7 intel quad core 6700k

Are you using LG? I have a 6700 and I can get 15 bots without LG.

Share this post


Link to post
Share on other sites

Spikes like that are attributed to either poorly written code or a very CPU-intensive method, more often the former than the latter.

Most commonly, I've seen people use for/while loops without any pause between loops, and that tends to cause a spike in CPU. There's tons of other things that could cause it though, so it's hard to say.

Java version, script, what it's doing when CPU spikes, LG/non-lg, computer specs, all come into play as well.

Share this post


Link to post
Share on other sites
5 minutes ago, Adventure_Time said:

Spikes like that are attributed to either poorly written code or a very CPU-intensive method, more often the former than the latter.

Most commonly, I've seen people use for/while loops without any pause between loops, and that tends to cause a spike in CPU. There's tons of other things that could cause it though, so it's hard to say.

Java version, script, what it's doing when CPU spikes, LG/non-lg, computer specs, all come into play as well.

Yeah I understand that. It can be hard to nail it down exactly. But realistically I figure I should be able to at least run 20 or so?

Share this post


Link to post
Share on other sites
6 hours ago, Duhstin said:

If using LG, don't use OSBuddy. Use the default RS client/browser. OSBuddy is a resource hog. I personally don't use LG.

all clients besides osbuddy have bugs when using LG on them.
 

8 hours ago, RSMAN96 said:

Nah man just injection. What is your CPU usage at 15? Perhaps I should mention this PC is only 2 days old.

i have the 6700k aswell and able to bot on ~10LG

Try 512mb Heap size & put your client paint delay to like 70. (its in the settings once you open the tribot client)

  • Like 1

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  

  • Our picks

    • This update will:

      Fix GE inventory item positioning bug


      Fix broken object hooks
        • Like
      • 21 replies
    • This release will:

      Fix some ClosedChannelException bug


      Fix bug in RSObject#getAllTiles


      Add game tab support for "Kourend Favour"
        • Like
      • 15 replies
    • This release will:

      Fix Settings UI placement bug


      Fix game object location bug


      Fix small layout bug making the client shift up and down


      Fix client crashing bug where loading the client with a small display area will cause the client to crash


      Fix annoying Linux bug relating to painting events and peers


      Fix settings saving bug where settings are saved to disk more often than they should


      Fix RSInterface#isBeingDrawn bug affecting a limited amount of people


      Drop Java 1.7 bytecode version for 1.8


      Important: Since the downloadable RS client uses Java 7, it will no longer be compatible with Looking Glass. To make up for this, we will add support for using other clients such as RuneLite (at a later date).


      This change was necessary to allow us to use Java 8 syntax. It also paves the way for Java 9/10/11 support.
        • Like
      • 40 replies
    • This update will:

      Fix the RSMenuNode bug which also fixes the bug with bank opening


      Fix the incorrect object positions bug


      Fix and re-enable the LG Objects API Accelerator


      Fix the RSObject#getAllTiles bug
        • Like
      • 22 replies
    • Try our development release by checking "Development Release" on the TRiBot Loader. Note that these new features are currently in beta.

      This release features:

      Re-sizable mode support for both LG and the regular client


      Slightly improved login bot


      Removed final access modifiers from API classes


      Added RSServer hook wrapper to get the client's cached list of server/world info


      [NEW] Bug fix for intelligent banking


      [NEW] Improvement to the stability of LG over time


      [NEW] Vastly improved the reliability and speed of Screen#getColorAt on both LG and the regular client


      [NEW] Fix LG login problems


      [NEW] Fixed re-sizable mode container bug


      [NEW] Fixed re-sizable mode mouse bug


      [NEW] Use of public constants in the Banking API


      [NEW] Use of other various constants such as Projection#NULL_PT and Screen#EMPTY_COLOR



      More features to come very soon!

      Please test it and let us know here if there are any new bugs introduced in this release.
        • Thanks
        • Like
      • 12 replies
  • Recently Browsing   0 members

    No registered users viewing this page.

×