Skip to main content
February 4, 2011
Question

CF9 Developer on Linux slow

  • February 4, 2011
  • 1 reply
  • 702 views

I have CF9 installed on Linux and it's exhibiting some odd behaviour

I have a simple test.htm file

When I do wget 127.0.0.1:8500/test.htm it pulls back instantaneously.

However when I do wget 192.168.1.50:8500/test.htm it takes nearly 45 seconds to respond (see below).

HTTP request sent, awaiting response... [rjasonc@localhost ~]$ wget 192.168.1.50:8500/test.htm

--2011-02-04 09:36:31--  http://192.168.1.50:8500/test.htm

Connecting to 192.168.1.50:8500... connected.

HTTP request sent, awaiting response...

Any thoughts?

    This topic has been closed for replies.

    1 reply

    Community Expert
    February 4, 2011

    It seems like the problem may be "public network interface is slow" rather than "CF 9 is slow". What happens when you fetch from another machine?

    Also, keep in mind that Developer does have limitations in the number of external addresses it'll allow to request pages - you might run into this while you're testing remote connectivity.

    Dave Watts, CTO, Fig Leaf Software

    http://www.figleaf.com/

    http://training.figleaf.com/

    Dave Watts, Eidolon LLC
    February 9, 2011

    It appears to be working now, but I wanted to go ahead and follow up.

    I had the following results.  The index.htm page is just "Hello" in standard html and body tags.

    Going through the CF9 development server on port 8500

    127.0.0.1:8500/index.htm              Pulled locally loaded instantly

    192.168.1.50:8500/index.htm         Pulled locally loaded in 45 -60 seconds

    192.168.1.50:8600/index.htm          Pulled from my laptop on the same network in 45-60 seconds

    Going through the default Apache server

    127.0.0.1/index.htm            Pulled locally loaded instantly

    192.168.1.50/index.htm      Pulled locally loaded instantly

    192.168.1.50/index.htm     Pulled  from my laptop on the same network loaded instantly.

    It was the darnest thing because Apache was loading it instantly, which suggested it wasn't a network problem.  That would imply ColdFusion was running slow.  However, it didn't run slow when pulling it using the local host ip.

    I'm still scratching my head.

    Like I said, the problem appears to have fixed itself, so I'm not sweating about it but still curious.

    Thanks!

    Jason