[aprssig] How to get new software evaluated???
andrewemt at hotmail.com
Wed Jan 25 14:03:40 CST 2012
Ouch! Did you open the IGate filter for a planetary feed? What filter did you specify?
I only tested YAAC with a half-planet feed (about 8000km radius filter), and it did bring my "iron" to heavy loading as well, though mine survived because my development system is a bit bigger than your server (I built it from gaming system parts and an 8-core CPU because modern Integrated Development Environments [IDE] are as resource hungry as any game out there).
Alas, I don't think things would have caught up if your Internet connection was saturated; I never saw the flood of APRS messages ever slow down significantly during my testing.. However, I will look into additional performance tuning.
YAAC was never intended to be an APRS-IS core server; it was aimed at the end-user, and field use when there is no Internet connection (only RF).
Andrew Pavlin, KA2DDO
Sent from my Verizon Wireless BlackBerry
From: ka7o <ka7o at ka7o.net>
Date: Wed, 25 Jan 2012 18:57:48
To: <aprssig at tapr.org>
Subject: Re: [aprssig] How to get new software evaluated???
Looks nice! Could be I don't have enough iron to use effectively though.
Just an old AMD Athlon at 3.2Ghz and 1G o RAM running Fedora 14.
I run my own I-gate/server here - connected up just fine, pulled the
feed. But, as soon as I connected, the system became unusable. %100 CPU
utilization, network similarly maxed out - YAAC became totally
un-responsive while populating stations on the grid (didn't even have
the maps setup, yet). An eventual CNTL-C in the terminal that launched
it and things are back. Cleaned up just fine.
Maybe if I'd let the firehose finish filling the pool, had more CPU
behind it or something. But, at first blush - that's the initial experience.
Note, this is a JAVA application - so, maybe if I'd given it more time
to catch up?
On 11/17/2011 01:20 PM, Andrew P. wrote:
> Greetings, all (especially WB4APR).
> As promised, I have a first (very early) cut of my new APRS application (currently code-named YAAC, for "Yet Another APRS Client" :-) waiting to be pounded on by experts in the field. It is not ready for full release quite yet (still have some source code clean-up and a few missing sub-features to add), but I would like to know if I'm doing the right thing or have majorly stumbled down the wrong path in my development efforts.
> So, I'd be interested in having Bob (and any others in the core of APRS development who are interested and have the time) take a whack at using my app, and tell me where I need to improve and/or correct it before I let it out to the general public.
> How is this sort of thing done here? I'm not ready to hand out source code yet (the innards aren't stable enough to have others tinker yet), but I can easily ship a zip file that unpacks a runnable distribution.
> Known working platforms are Windows XP (NTFS filesystems only, for some weird reason) and Fedora Core Linux (releases 13 and 15, with a hack needed on 15). It should work on any 32-bit Windows or Linux distro with Java installed, and theoretically should work on MacOSX too. It can listen to APRS-IS servers, and both receive and transmit through KISS (or KISSable by TNC2 command) TNC's, and listen to Kenwood radios in APRS mode (Kenwood firmware doesn't seem to allow transmitting APRS from the radio and a computer simultanously). It also works with NMEA 0183-compliant GPS receivers (not yet with gpsd in the way). App configuration is done inside the app with a configuration GUI; no need to hand-edit config files.
> So, how do I get some initial alpha-test field feedback?
> Andrew Pavlin, KA2DDO
> Sent from my Verizon Wireless BlackBerry
> aprssig mailing list
> aprssig at tapr.org
aprssig mailing list
aprssig at tapr.org
More information about the aprssig