Jump to content

.:MARK:.

Member
 View Profile  See their activity

  • Posts

    567

  • Joined

  • Last visited

Awards

This user doesn't have any awards

20 Followers

See all followers

Profile Information

  • Gender
    Male
  • Location
    schnitzel.team
  • Interests
    hacking, programming, networking and messing about. Basically anything but gaming.
  • Member title
    Schnitzels

System

  • CPU
    Intel Core i7 3770K
  • Motherboard
    ASRock z77 Extreme 4
  • RAM
    Kingston HyperX 1600MHz 16GB
  • GPU
    Zotac 980Ti
  • Case
    NZXT Phantom
  • Storage
    Samsung 840 Pro 128GB
  • PSU
    Corsair AX860
  • Display(s)
    2xP2415Q
  • Cooling
    Cryorig H7
  • Keyboard
    G610
  • Mouse
    Performance MX
  • Sound
    HD598SE

Recent Profile Visitors

2,941 profile views

.:MARK:.'s Achievements

Collaborator

Collaborator (7/14)

220

Reputation

5

Community Answers

  1. .:MARK:.
    When it comes to samba performance on android, I've not been able to get any better speeds than you. I don't think it's a problem you can fix.
  2. .:MARK:.
    Make sure QoS is off, make sure DPI is off, make sure HW offloading for everything is on. Though the X is a poor choice, I would at least go with an EdgeRouter Lite.
  3. .:MARK:.
    You know why.
  4. .:MARK:.
    Go intel because it's better
  5. .:MARK:.
    Most of this is false. A game doesn't "pull memory" from a hard drive. And issues with registry are unlikely if the setup is done properly. To execute a game, the operating system will load the binary into RAM. In order to do that, the operating system will fetch it using it's own layers of abstraction that allows it to treat network filesystems like local ones, especially solutions like iSCSI. When an iSCSI disk is mounted, to all programs on the computer it appears as any other disk and is able to access it using the same filesystem API as it does for local disks. The game binary is able to read resources from the mounted filesystem as it uses the operating system's filesystem API and it works as normal. Issues with registry should not exist as long as paths remain constant. As @leadeater mentioned, a good 10Gbit NIC is nice to have, I prefer Intel ones such as the X520 DA2. And the nicest protocol for this is iSCSI, as this works more like a true disk rather that a mapped network disk. And you'll likely have faster speeds than a SATA 3 SSD (given you exceed 6Gbit/s).
  6. .:MARK:.
    @leadeater @dalekphalm I'm curious since I am helping someone build a ZFS array right now. I have a few questions. First of all, I might add I don't care about ECC or non ECC, to me it makes no sense to argue over it. But I am curious about the behaviour of the filesystem itself, how it can be bottlenecked by certain types of loads and how it will deal with those bottlenecks. If someone can provide or link to a good explanation of different kinds of loads on the filesystem and how it stresses resources, then a mythical rule of thumb won't be necessary. So if one of you can briefly give an example of a load, and how the filesystem deals with it and then what resources it uses for that, then maybe we can get a better idea of how the lack of a certain resource will impact performance. For example if I have no deduplication or compression enabled on a zpool with 2 vdevs of 8x2TB drives in Z2 and no ZIL or L2ARC. And I do a write over iSCSI with 10Gb connection, how does the filesystem handle the writes, and what resources will it use?
  7. .:MARK:.
    If you want your traffic to be encrypted so that your ISP cannot view it, you need to control a node outside of your ISP network and make a secure connection to that. Then give people the address to that node (a VPS for example) and ask them to connect to that instead. What you should do is forward all the traffic on those ports on the node to your home through a VPN connection. That way, all traffic from you would go through that node before it leaves to go anywhere else on the internet, and all traffic from the internet would go to that node and travel through a encrypted link before it hits your home.
  8. .:MARK:.
    I personally prefer nginx, it's usually faster and easier to configure.
  9. .:MARK:.
    I stay away from infiniband entirely, getting IP over infiniband is spotty. And as above, drivers are usually a pain or don't exist at all.
  10. .:MARK:.
    Pretty much anything running on x86 will work better with fq_codel, the EdgeRouters have a very low power MIPS chip in them.
  11. .:MARK:.
    To add to this, the QoS basically removes the ability to run HW offloading as it manages queues in software, you'll basically get 80-100Mbit/s speeds using QoS. Though I really doubt that you'll need any kind of QoS on a gigabit line.
  12. .:MARK:.
    The larger flash is not just an advantage, but a requirement. The ER-X can't even update successfully because of how tiny that flash is.
  13. .:MARK:.
    Personally I want a homelab thread, where people can actually explain and show off their systems/clusters and networks. That's when I'll bother posting my stuff.
  14. .:MARK:.
    Click each partition and click delete. Then you will have one item left (called "Unallocated Space" or something similar), then just select it and click next.
  15. .:MARK:.
    The storage server is designed to be functional standalone and also somewhat portable (as portable as several Us of rackmount gear can be). The virtualisation servers run a whole lot more VMs running many services. The connection between me and looney isn't great, but the most important services are HA and failover. I'll work on a network diagram for me and @looney when were done with most of the work.
×