|
|
| Author |
Message |
|
| knotwell at f5.com |
 Posted: Thu Apr 29, 1999 9:28 pm |
 |
|
|
Guest
|
Hello all--
I was able to compile Erlang 47.4.1 under BSDI3.0 (jam only). Beam
wouldn't compile because erlc was complaining about running out of
memory. I'm guessing that having more than 64MB of memory available
would've helped.
First some observations:
1) It appears that an install program compatible with GNU's install
is required. The default install on BSDI blew up on the -d option.
Resolution: use fileutils package found at ftp.gnu.org
2) the configure script checks for pthreads as a separate library.
Under BSDI3.0/3.1, the pthreads functions are found in libc instead of
libpthread.
Resolution: not really a problem I suppose. I suppose it would
degrade performance some.
Question: does anyone have a SWAG about how much performance is lost
when multiplexing in a single-thread/process???
3) lastly (and most interesting), my source code didn't work the
same between a redhat linux system and a BSDI system. The BSDI system
complained about a nxdomain error. I'm kind of surprised at this as
it appears to have something to do with a the system being unable to
do a host name lookup. The BSDI and Linux box both queried the same
name on the same name server. . .pretty curious.
Question: anyone have any quick ideas on this one? I could certainly
fire up the debugger, but I thought I'd ask for any quick suggestions
(since I'm not certain how easy it will be to compile up the graphics
stuff under BSDI  ).
Thanks.
--Brad
Post generated using Mail2Forum (http://m2f.sourceforge.net) |
|
|
| Back to top |
|
| knotwell at f5.com |
| Posted: Fri Apr 30, 1999 9:24 pm |
|
|
|
Guest
|
knotwell_at_f5.com writes:
> 3) lastly (and most interesting), my source code didn't work the
> same between a redhat linux system and a BSDI system. The BSDI system
> complained about a nxdomain error. I'm kind of surprised at this as
> it appears to have something to do with a the system being unable to
> do a host name lookup. The BSDI and Linux box both queried the same
> name on the same name server. . .pretty curious.
Resolver notes:
The program seems to work if I use dot addresses. I guess this points
even more highly towards a problem with the resolver.
Beam compilation:
I previously received a "couldn't reallocate" error, with a
suggestion from Mr. Tornkvist, I increased some of the system
limits for BSDI.
First, I recompiled the kernel with the DFLDSIZE and MAXDSIZ
increased to 128M and DFLSSIZ set to 8M. I then set the datasize,
stacksize, memoryuse, and memorylocked system limits as large as
possible. Jam was then able to compile everything correctly.
Performance improvement:
Using the beam compiler, my application's (a braindead traffic
generator), connection rates went from 120-130 connections/s to
160-180 connections/s. All in all, beam gave me nifty 50% performance
gain.
Thanks.
Brad
Post generated using Mail2Forum (http://m2f.sourceforge.net) |
|
|
| Back to top |
|
|
|
All times are GMT
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You cannot download files in this forum
|
|
|
Digg It
Del.icio.us
Reddit
Facebook
Stumble Upon
Technorati
