NETIO_MTSERVER on new hardware is much slower than expected

[Lorenzo Fiorini]

Hi all,

I'm trying to upgrade an installation that is using a Linux server with Ubuntu 18.04.5 LTS 32bit since years as a NETIO_MTSERVER with a newer hardware with a Debian 12 64bit but the new setup is much slower than the old one (5-6 times slower).

It's not a hardware or a network problem since I get the same bad result in my office even with a much more powerful hardware.

I've tried to change several sysctl parameters and I've also tried to use the very same NETIO_MTSERVER 32bit code that I use in old Ubuntu without success.

As a comparison I've tried to install Samba and set a simple share and it seems quite fast, surely faster than the old setup and much much faster than the new setup.

Any suggestions?

Regards,

Lorenzo

[Gerald Drouillard]

Tell us more about what the netio server is slow at.  example:  dbf access?

--
You received this message because you are subscribed to the Google Groups "Harbour Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to harbour-deve...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/harbour-devel/CAB9-wYsj2%3DEKmUdFTKq1WsORamX0GVSEVM_BtzOGSbOys6PKkQ%40mail.gmail.com.

[Lorenzo Fiorini]

On Mon, Jan 22, 2024 at 7:18 PM Gerald Drouillard <ger...@drouillard.ca> wrote:

Tell us more about what the netio server is slow at.  example:  dbf access?

It is a very simple Harbour app, that I have used almost untouched for years, that "serve" a folder of dbf/cdx files via a TCP port using pretty standard NETIO_MTSERVER() code. Windows clients connect to it using NETIO_CONNECT() (see contrib/hbnetio).

This client/server setup has been working flawlessly for years. What I wanted was simply faster data access.

 

To view this discussion on the web visit https://groups.google.com/d/msgid/harbour-devel/CAC_Y%2BMDeycBDpgc0o3goTC7%2BaQ-oEdkGDbOrFqj7gr6tGZzWCw%40mail.gmail.com.

[Gerald Drouillard]

Did the file system change?  Disk r/w rates?

Test network I/O against the new server?

Memory, cpu usage?

caching policy

Look in the kernel, system logs?

What is slow?  locking? opening?  seeks?  Does the size of the file matter?  

Are the dbf's also available via samba?  Maybe you have a windows machine virus scanning the file(s) on access?

To view this discussion on the web visit https://groups.google.com/d/msgid/harbour-devel/CAB9-wYsQ2C%3DacXC2ZLCQjqy3VTup2r8kzgZj6fi3419R-Pn8zQ%40mail.gmail.com.