Main > Everything Else

Workflow server

Pages: (1/5) > >>

sdweim85:

The company I work for asked my opinion on a new project that is ongoing which is bogging down on server tremendously.  The way our network is setup is that everyone just has their own desktops and they just get their work from a fileshare on a server that houses all the projects.  They basically just open up 1000 thumbnails jpegs and look for mistakes.  Thing is when more than 6 people start viewing thumbnails they all start going really slow.  Everyone is on a gigabit connection with i3s, and the server is a Xeon 3.40ghz 16 gigs of ram server 2008 r2. 

a few thousand dollars worth of equipment and no more than 6 people view thumbnails over the network simultaneously?  How do mega corporations get by?  Is it all hardware based?  Or is there something i'm missing, like the users log into a virtualized server through hyper V to do their work.  So instead they are using the server hardware instead of relying on network bandwidth to view images.

kahlid74:

You've got a lot going on here but you're still limited to 1000Gbe which translates into ~ 120MB/s.  Realistically 6 computers can max that out if they are all transferring at the same time. 

Can you give more details specifically about your application and how it accesses the thumbnails?  Or are users just opening up a folder and the thumbnails are populating?

kegga:

There could be a lot of potential bottle necks here:
Storage are the files on a SAN or Local disk to the server, what is the raid level, what speed are the disks. If on a SAN are you seeing any read latency issues?
On the Network how are the switchs configured is it true 1Gb or a shared backplain, Are there any mismatches between speed and duplex settings of the clients and switch ports?
As you can see there are a lot of things that can be checked before you go making major changes.

MonMotha:

If I had to guess, you're bottlenecked on disk IO on the server.  I've got 6 Xen domains running on a server nowhere near that capable CPU-wise (and less memory, and probably less memory bandwidth, too), and my bottleneck is ALWAYS the darned spinning metal.  Lots of simultaneous requests for distinct files like you describe will easily get you well into seek hell.  Throw an SSD at the thing if you can, and your problems will probably get better.

Failing that, upgrade the server's link to the LAN to 10Gb or 4xGbE.  Make sure you've got a real switch, not some crummy Linksys thing.

Of course, real stats are always king.  Instrument the heck out of the setup and see where your problems actually are.

Malenko:

Have you done any monitoring to see what the actual slow down issue is? Check the logs or set up a resource monitor.
Dont guess what will fix it, find out whats broken first.

Pages: (1/5) > >>

Go to full version