Jump to content

Diabloz

Members
  • Posts

    210
  • Joined

  • Last visited

Posts posted by Diabloz

  1. On my server i have rules about machines, factories and large factories, what is ideal, and guidelines to "large" factories. When i say an admin to clean up, its mostly an Admin who enforces the factories rules and guidelines, if the machine/factory isnt up to regulations the factory gets quarantined (all energy sources are isolated and air blocks around and inside the machine are replaced with bedrock. It's not fair that one player builds laggy factories and ruins it for others who build their factories according to the rules and guidelines.

  2. You both mis-understood me.

    I was replying to Watchful. I'm meaning if he were to remove the code to pervent people from using to crash servers then how

    else would people get the fix? Pming him? He's going to get pinned in a corner. Anyways, when you have exploits out the in opened. They get fixed faster.

    All major security enterprises do this, Cisco would be a prime example.

    You're right, but to watchful, the crashing code isn't there anymore so it shouldn't be an issue anymore, sorry for miss understanding.

    Besides only very experience CC players have the ability to find this code in the first place, Most will do this for fun and will usually keep this code to them selves so other can't find a fix. You shouldn't be worried about this as long as you do this code.

  3. Then how do we stop it? We gotta have to code in-order to stop it.

    this is the fix as he posted all you need to do is follow his instruction:

    For example:

    BBUnx.png

    As stated by matejdro:

    FIX:

    Add this to the end of the /mods/ComputerCraft/lua/rom/startup :

    Code:

    oldRedstoneFunction = rs.setOutput

    rs.setOutput = function(side, bool)

    sleep(0.05)

    oldRedstoneFunction(side, bool)

    end

    Or you could stop it by just typing in at the top

    oldRedstoneFunction = nil

  4. Name:prowder

    Age:23

    What do you wish to accomplish?:a chest full of diamonds

    Have you played IC2 or buildcraft? no

    what is the purpose of a macerator? dont know

    Recommendations(if you been invited):nothing really

    Others things i should know:nothing special

    Name:tupelAge:23

    What do you wish to accomplish?:a chest full of diamonds

    Have you played IC2 or buildcraft? no

    what is the purpose of a macerator? dont know

    Recommendations(if you been invited):nothing really

    Others things i should know:nothing special

    re-apply

  5. I am not really understanding what you are trying to say, about the disk IO.

    if you are trying to say its something to do with the formatting of the HDD on the server, then thats nothing i can go and change (its my schools servers)

    Turns out, i incorrectly posted about the server ITS A WINDOWS SERVER so there is no /var/log/messgaes.

    We (me and the scholl technician) tried doubling the ram put into the server, no help.

    any more ideas?

    hes refering to you HDD I/O (inputs and outputs; (taken from http://blog.scoutapp.com/articles/2011/02/10/understanding-disk-i-o-when-should-you-be-worried) to read full article click the link.

    Do you have an I/O bottleneck?

    Your I/O wait measurement is the canary for an I/O bottleneck. I/O Wait is the percentage of time your processors are waiting on the disk.

    For example, lets say it takes 1 second to grab 10,000 rows from MySQL and perform some operations on those rows.

    The disk is being accessed while the rows are retreived. During this time the processor is idle. It’s waiting on the disk. In the example above, disk access took 700 ms, so I/O wait is 70%.

    You can check your I/O wait percentage via top, a command available on every flavor of Linux:

    If your I/O wait percentage is greater than (1/# of CPU cores) then your CPUs are waiting a significant amount of time for the disk subsystem to catch up.

    In the output above, I/O wait is 12.1%. This server has 8 cores (via cat /proc/cpuinfo). This is very close to (1/8 cores = 0.125). Disk access may be slowing the application down if I/O wait is consistently around this threshold.

    What impacts I/O performance?

    For random disk access (a database, mail server, file server, etc), you should focus on how many input/output operations can be performed per-second (IOPS).

    Four primary factors impact IOPS:

    • Multidisk Arrays – More disks in the array mean greater IOPS. If one disk can perform 150 IOPS, two disks can perform 300 IOPS.
    • Average IOPS per-drive – The greater the number of IOPS each drive can handle, the greater the the total IOPS capacity. This is largely determined by the rotational speed of the drive.
    • RAID Factor – Your application is likely using a RAID configuration for storage, which means you’re using multiple disks for reliability and redundancy. Some RAID configurations have a significant penalty for write operations. For RAID 6, every write request requires 6 disk operations. For RAID 1 and RAID 10, a write request requires only 2 disk operations. The lower the number of disk operations, the higher the IOPS capacity. This article has a great breakdown on RAID and IOPS performance.
    • Read and Write Workload – If you have a high percentage of write operations and a RAID setup that performs many operations for each write request (like RAID 5 or RAID 6), your IOPS will be significantly lower.

×
×
  • Create New...