typing in SSH laggy / unresponsive?

[greebles]

I'm new to FreeNAS. I just built a FreeNAS-9.2.1.2-RELEASE-x64 version on an ASRock C2750D4I with 16gb ECC RAM (8x2) and 6 3tb WD Reds in RAIDZ2. FreeNAS is installed on a 16gb SanDisk Cruzer USB flash drive.

The build has gone relatively smoothly, and last night I copied my first hunk of files to it, around 30 GB I believe, and it was extremely fast, around 95 MB/s or so. Coming from a lethargic QNAP TS-409, this was quite pleasing.

However, I've had one bit of trouble: when I SSH into the box (from the same network, and using a variety of SSH programs), the experience is often laggy, where the terminal won't get what I'm typing. I'll type commands in, and it'll "stop listening" half-way through, then get the rest of the command in a few seconds. It's very frequent, too.

I'm no UNIX guru by any means, but e.g. when I SSH into my low-powered Acer AspireRevo 1600, it's never had this problem, so I can't imagine what's causing this on what's a much more powerful machine.

Now once I get setup, I don't imagine I'll be SSHing into the box all that much, so if this is the only problem, not a huge one, but it definitely seems weird, and is definitely annoying.

Any thoughts? Thanks!

EDIT: wanted to add, I have both gigabit ports plugged in, and create a "lacp" Link Aggregation. Everything seemed to work fine, but while my networking knowledge is ok, I'm by no means an expert. I know the router needs to also support link aggregation, but to be honest, I have no idea if the one I have does. I just set up the LA, saw that I could still see the box, copy files, etc, and was done with it.

But I suppose since this SSH issue seems like a "laggy" network, maybe that could have something to do with it. I can try removing the link aggregation, and just using one port. I'm assuming that without aggregation, it doesn't do me any good to have both ports wired up?

 

[cyberjock]

It sounds to me like your lacp may be causing problems. If you are a home user there's no reason to use lacp, but dozens of reasons not to. I'd try disabling lacp first and see if that fixes it.

You do not want both ports wired up and on the same subnet as the other port.

 

[jgreco]

I'll buy the LACP but would suggest alternatively that packet loss of any other sort could be causing that sort of thing too. Run a long ping, maybe 1000 iterations. You can also try the same with a large packet size.

 

[greebles]

Update: I removed the LACP, and now SSH seems silky smooth. Appreciate the help!

 

[cyberjock]

And those dozens of reasons to not use LACP has bitten another victim.