Jump to content
Search In
  • More options...
Find results that contain...
Find results in...
wkw7392

VPS Concerns

Recommended Posts

Hi there,

brand new here and I have a few questions if anyone feels like answering.

Firstly, I want to start out by saying I'm new to this. I am looking at going through and taking some time to attempt botting and practice to really get down the methods. I was intending on using some small Amazon EC2 instances to get started and find out what works. Won't have to pay hardly anything, a new IP address on each instance, and I can spin it down and spin another up in 15 minutes. However, if things were to begin to expand, and I were wanting to give this a bit of scalability, I intended to purchase a bare metal hosted server that I can run as a VM host. Likely linux based using Virtual box for the guest OS's.

 

I have my eye on a hosted Linux server with Dual Quad Core Xeon X5560's and 96 GB of RAM that I can get for 50 bucks a month provided I can do this all via linux. I plan on splitting this into several lightweight XFCE ubuntu guests with around 4GB or 8GB of RAM each. My first question would be, how many bots do you think I could get going from this setup, and would it be safer to have more guests with less bots with 4GB of RAM each, or the reverse with 8GB of RAM each?

Secondly, I intend to run the guests through its own proxy. Am I correct in thinking that that would prevent my host IP from being blacklisted?

 

And before anyone says, I'm diving in to deep to early, I was probably going to get this thing up and running anyway for my own personal side projects. :)

 

Any help or suggestions would be appreciated!

Share this post


Link to post
Share on other sites
4 hours ago, wkw7392 said:

I have my eye on a hosted Linux server with Dual Quad Core Xeon X5560's and 96 GB of RAM that I can get for 50 bucks a month provided I can do this all via linux. I plan on splitting this into several lightweight XFCE ubuntu guests with around 4GB or 8GB of RAM each. My first question would be, how many bots do you think I could get going from this setup, and would it be safer to have more guests with less bots with 4GB of RAM each, or the reverse with 8GB of RAM each?

Forgive me for asking, but why would you split it into guests anyways? Assuming you're using the entire server for botting, setting up guest environments would just introduce overhead you wouldn't need. But as for how many bots, usually the cap on that is CPU and not RAM requirements, and sadly those requirements change per script, as some are more resource intensive than others. You'd have to play with that as well. I'd personally be more inclined to lean towards the bigger guests with 8GB of RAM each? As it'd reduce the overhead again, due to less splits.

4 hours ago, wkw7392 said:

Secondly, I intend to run the guests through its own proxy. Am I correct in thinking that that would prevent my host IP from being blacklisted? 

Yes exactly!

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


  • Our picks

    • This update features:

      Fixed broken hooks from today's update


      Fix wilderness level with RuneLite (Thanks @Todd)


      Add support for Kotlin .class files in scripts (Thanks @wastedbro)


      Overhaul Inventory API (Thanks @wastedbro)


      Add List support for common methods


      Change method grouping to make more sense (by functionality)


      Refactor methods to utilize Java 8 streams instead of cumbersome loops




      Recognize chatbox minimization (Thanks @JoeDezzy1)


      Fix Screen#isInViewport when NPC chat is open (Thanks @JoeDezzy1)


      Fix login bot bugs (Thanks @erickho123)


      Fix hint arrow return values (Thanks @Encoded)


      Fix depositAllExcept functionality (Thanks @wastedbro)


      Change containing box interface bound and adjust for Y values (Thanks @erickho123)
        • Like
      • 151 replies
    • This release will:

      Fix prayers and world hopper API (Thanks @JoeDezzy1 and @erickho123)


      Improve banking API (Thanks @Encoded)


      Adds methods for returning and using Java Lists, rather than arrays


      Slightly randomizes some hardcoded behaviour


      Removes sleeps from waitConditions; the efficiency saving potential is negligible in these use-cases, therefore cleaner code is preferable


      Other back-end improvements





      Note: If you are using LG, please restart both the RS client and TRiBot.
        • Sad
        • Haha
        • Thanks
        • Like
      • 90 replies
    • This release will:

      Add new internal framework for capturing exceptions


      Fix issue with not selecting the last column in world hopper (Thanks @Todd)


      Add a message about pin usage in Banking#openBank (Thanks @Todd)


      Disable the firewall by default (Thanks @Todd)


      Fix handling of the welcome screen after login (Thanks @Encoded)


      Fix wrong amount bank withdrawal (Thanks @Encoded)


      Fix Screen#isInViewport


      Fix Game#isInViewport (Thanks @Encoded)


      Call onBreakEnd for ListenerManager Breaking Listeners (Thanks @Encoded)


      Fix Prayer#getPrayerPoints NumberFormatException (Thanks @JoeDezzy1)



      Note: If you are using LG, please restart both the RS client and TRiBot.
        • Thanks
        • Like
      • 28 replies
    • This release will:

      Fix LG for both OSBuddy and RuneLite


      Fix issue where the resizable client isn't able to be made smaller (Thanks @JoeDezzy1)


      Fix detection of the logout game tab when resizable mode and side panels are enabled (Thanks @JoeDezzy1)


      Add initial support for Sentry to allow us to identify and easily debug exceptions happening with all TRiBot users


      Add methods to determine if the bank is actually loaded, and not just the overarching interface (Thanks @wastedbro)



      Upcoming updates:

      Improved CLI support


      Full Sentry support


      Much more
        • Like
      • 64 replies
    • This release will:

      Fix NPE in Camera API (Thanks @wastedbro)


      Update deposit box interface ids (Thanks @Encoded)


      Add various bank methods (Thanks @wastedbro)


      Banking#getWithdrawXQuantity


      Banking#getDefaultWithdrawQuantity


      Banking#arePlaceholdersOn




      Fix resizeable minimap bug (Thanks @wastedbro)


      Remove Java 8 requirement


      Please note: TRiBot is not yet fully compatible with Java 10+




      Fix the break handler issues by ensuring the break handler thread never gets paused


      Fix broken settings hooks



      Upcoming updates:

      Improved CLI support


      Much more



      Note: If you are using LG, please restart both the RS client and TRiBot
        • Like
      • 68 replies
  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...