static library to sockets on localhost

Collapse
This topic is closed.
X
X
 
  • Time
  • Show
Clear All
new posts
  • call_me_anything

    #1

    static library to sockets on localhost

    Hi,

    We had a library linked dynamically in our 32 bit mode.
    Now due to capacity issues, we are planning to move on to 64 bit but
    the library is still 32 bit and
    we cannot make it 64 bit without a mammoth effort.
    So we decided to use IPC via sockets such that the library calls are
    run on a 32 bit machine while
    our application runs on a 64 bit machine.
    But that is slowing down the things by a factor of say 100.
    Is this expected ?

    I am using Tcl sockets for this purpose and right now, both the
    processes are running on the same machine.
    Our application built in 32 bit mode to test the IPC mechanism.

  • Gianni Mariani

    #2
    Re: static library to sockets on localhost

    call_me_anythin g wrote:
    Hi,
    >
    We had a library linked dynamically in our 32 bit mode.
    Now due to capacity issues, we are planning to move on to 64 bit but
    the library is still 32 bit and
    we cannot make it 64 bit without a mammoth effort.
    So we decided to use IPC via sockets such that the library calls are
    run on a 32 bit machine while
    our application runs on a 64 bit machine.
    But that is slowing down the things by a factor of say 100.
    Is this expected ?
    Well, yes. It depends on how much you're calling and waiting for your
    32 bit library.
    >
    I am using Tcl sockets for this purpose and right now, both the
    processes are running on the same machine.
    Our application built in 32 bit mode to test the IPC mechanism.
    Sounds like it's time to re-write your 32 bit DLL, or at least the bits
    you use.

    Comment

    • =?ISO-8859-1?Q?Erik_Wikstr=F6m?=

      #3
      Re: static library to sockets on localhost

      On 2007-09-16 10:21, call_me_anythin g wrote:
      Hi,
      >
      We had a library linked dynamically in our 32 bit mode.
      Now due to capacity issues, we are planning to move on to 64 bit but
      the library is still 32 bit and
      we cannot make it 64 bit without a mammoth effort.
      So we decided to use IPC via sockets such that the library calls are
      run on a 32 bit machine while
      our application runs on a 64 bit machine.
      But that is slowing down the things by a factor of say 100.
      Is this expected ?
      >
      I am using Tcl sockets for this purpose and right now, both the
      processes are running on the same machine.
      Our application built in 32 bit mode to test the IPC mechanism.
      For future questions like this please use a group discussing your
      platform or the libraries you are using, the question is off topic here.
      The fact that the code was written in C++ (it was right?) does not make
      the question topical.

      As to your problem, what you are doing now seems to be RPC (Remote
      Procedure Call) not IPC (Inter-process communication) so my suggestion
      is that you try to use IPC instead. Wrapp the library in a small
      application which is then run in 32-bit mode on the 64 bit computer.
      Then the 64-bit application and the library can communicate via IPC
      messages. Depending on your usage you might not notice any slowdown at all.

      --
      Erik Wikström

      Comment

      • James Kanze

        #4
        Re: static library to sockets on localhost

        On Sep 16, 10:21 am, call_me_anythin g <sgiitne...@gma il.comwrote:
        We had a library linked dynamically in our 32 bit mode.
        Now due to capacity issues, we are planning to move on to 64 bit but
        the library is still 32 bit and
        we cannot make it 64 bit without a mammoth effort.
        Isn't it sufficient to just recompile it?
        So we decided to use IPC via sockets such that the library calls are
        run on a 32 bit machine while
        our application runs on a 64 bit machine.
        But that is slowing down the things by a factor of say 100.
        Is this expected ?
        It might be. It depends on a lot of things. Most of which are
        system dependent: under Unix, for example, you should ensure
        that you are using Unix domain sockets, and not TCP. You'd best
        ask in a group specific to your OS.

        --
        James Kanze (GABI Software) email:james.kan ze@gmail.com
        Conseils en informatique orientée objet/
        Beratung in objektorientier ter Datenverarbeitu ng
        9 place Sémard, 78210 St.-Cyr-l'École, France, +33 (0)1 30 23 00 34

        Comment

        Working...