Home
Arrow Trader Lite
Arrow Trader Lite III
Arrow Trader eXtreme
Resources
Contact Info
Public Forum
|
Jan 15 - 2008
Arrow Scripts site updated
Jan 01 - 2008
Work has begun on ATX 2
Jan 01 - 2008
Happy new year :-)
Dec 10 - 2007
Xmas action launched
Dec 08 - 2007
ATX 1.3 + ATL 3 updated
(atx 1.3.08 & atl 3.16)
Oct 01 - 2007
ATX 1.3 updated
(atx 1.3.07)
|
XXX Host It
Our host since many years!
Smart Thumbs
Swiftwill, Inc.
Croc Network
Arrow Scripts
|
|
Besides pointing out some of the best features of ATX,
this page also provides you with more technical information,
like how ATX works, and what is required to make it work.
Please read it carefully so you know what you can expect.
|
Without doubt still one of the most important things is that ATX is written in the programming language C++.
Speed-wise this script leaves the competition (especially php / asp / perl scripts) FAR behind.
My own FreeBSD box (click for more info) processed over 15 million hits / day easily with a system load less than 2!.
So (a lack of) speed is no longer an issue.
How this is possible? click here for a metaphor that explains it
|
ATX has been given Artificial Intelligence, a virtual brain, that learns from the past, and then changes
the way traffic is being returned to your trades, in such a way that gives maximum growth.
No longer will the size of your site be limited by a poorly designed "one-size-fits-all" return function.
ATX adjusts itself to the needs of your site because every site is unique and requires a different approach.
|
Cheaters and hitbots are getting smarter by the day, and so our counter-measures must advance as well.
ATX offers you some very innovative tools to detect different types of cheaters.
For example, the Site-Compliance-Spider can visit all your trades several times per day and check for pop-ups,
dialers, auto bookmarkers, redirections, server errors, etc. and report this to you, or disable the trade entirely.
The most destructive of cheaters, like hitbotters can be filtered out now, via custumizable botlinks, detailed log files
with all sorts of proxy / country / header / IP information, and of course built in bot-filters that block a bot directly.
|
To grow a massive digital empire, time is the one thing you cannot spare.
With ATX you now have the power to monitor and control ALL your sites from a single admin panel.
Want to share a blacklist? A search engine list? Or do you want to export 100 trades from one site to another?
Do it with one click and it works instantly across ALL your domains.
|
With a template driven admin panel, you can select from a massive 38 recorded statistics to be displayed.
Customise the template by adding and removing the features you want and know are most valuable to you.
Change templates to suit your current objective. To focus on growth or cheaters for example,
simply select the one you need from the handy drop down menu.
Customise the style and feel with cascading style sheets (css).
No longer do you have to put up with the look that the author prefers, with ATX you can create your own.
|
Besides all the obvious features, ATX has several unique features that you won't find in any other trade script.
For example, you can give the traffic of every trade a different skim percentage from the script, without
having to adjust your actual html page.
There are a lot of features for nocookie traffic, exout traffic
(there's a free exout-rotator available on arrowscripts.com as well!). You can give trades different colors
in the admin so you can keep a close eye on them. The toplist supports titles, descriptions and images,
so you can present your trades in any way you want.
ATX also allows you to track the statistics of ALL
the search engines that you can think of as one individual trade. So you don't have to add google.com
google.de google.fr google.co.uk google.co.jp google.co.kr google.com.com as individual trades anymore.
ATX supplies a list of about 150 search engine domains already, covering the biggest SE's of the moment.
And of course, there's much much much more!
|
Despite it's complexity, ATX doesn't require much to run on.
Before your order, make sure that your server runs / supports the following:
- Crontab
The crontab is a small background service that runs whatever you want it to every minute.
ATX uses the crontab to read the log files of incoming and outgoing hits every minute,
to update the stats, re-calculat the value of all the trades, update the toplists,
scan your trades, and some other minor processes.
- FTP + SSH access
In order to upload and install the script, FTP (to upload) and SSH (to install) is required.
A 'root' account is not required for SSH. In fact, the user account that matches the rights and
permissions of your own account is preferred.
- cgi-bin
ATX is compiled in C++. The resulting binary code uses the Common Gateway Interface (CGI)
to communicate with Apache and basically work. Therefore it is required that apache is set up
to execute cgi files in a specific directory. Usually this directory is called 'cgi' or 'cgi-bin'.
So make sure your host supports cgi files!
- chmod
The CHMOD command is required to change the permissions for certain files.
CHMOD is a very basic command that all professional hosts support.
Occasionally the CHOWN command is also required to change the ownership of certain files.
If you have a SSH account for your users account on your server CHOWN is probably not required.
- One of the following Operating Systems
- FreeBSD 4.x
- FreeBSD 5.x
- Redhat 7.x
- Redhat 8.x
- Redhat 9.x
- Debian 2.x
- Debian 3.x
- Slackware 8.x
- Slackware 9.x
if your server runs a different distro / version of Unix / Linux,
please send an email to support at arrowscripts.com first.
Other distros will most likely work, but these are the ones that have been tested so far.
If your host gives you the choice, always go for FreeBSD :)
|
Why is C++ quicker?
C++ is like the tourist who takes time to learn the language of the country before he visits.
Since they know the language, they don't need to keep referencing translators to find out what needs to be done.
Other languages constantly require referencing to work out what needs to be done,
thus making them inefficient in comparison to C++
For more information about C++ please visit http://www.research.att.com/~bs/C++.html
which is the website of the designer of C++!
|
The benchmarks were performed on a server with the following specifications
- FreeBSD 5.2.1 - AMD64 Platform
- Apache 1.3
- AMD64 3200+ CPU @ 2.05 GHz
- ASROCK K8S8X @ 10x205, SIS755 Chipset
- 1024MB (2x512) DDR 400 RAM (TWINMOS) @ 200MHz CL 2.5
- MAXTOR 6 Y120M0 SCSI (120 GB, 7200 RPM, SERiAL-ATA/150)
The benchmarks were performed by a program that creates a socket, connects to apache,
sends the GET request to a index page with in.cgi or to out.cgi, and receives the response,
so the process in theory is the same as with real life surfers.
To give apache and the script some extra work all possible environment variables were filled in,
like http_referer, http_user_agent, http_via and http_cookie, so those all could be loaded.
The out.dat file contained 35 trades to give out.cgi an average workload.
To simulate simultaneous surfers requesting documents at the same time we ran several copies
of the socket program simultaneously as well. The server load was monitored via the 'TOP' command
| Benchmark 1) -- 15kb .shtml file with in.cgi via ssi | |
| Number of Requests | Time Taken (seconds) | |
| 100 | 0.524 | |
| 500 | 2.699 | |
| 1.000 | 5.350 | |
| 5.000 | 26.963 | |
| 25.000 | 2m 15s | |
| 100.000 | 8m 58s | |
| 1.000.000 | 1h 27m 30s | |
| 10.000.000 | 15h 10s | |
| 15.982.241 | 24 hours * | |
| * by calculation | |
| Benchmark 2) -- direct out.cgi | |
| Number of Requests | Time Taken (seconds) | |
| 100 | 0.681 | |
| 500 | 2.894 | |
| 1.000 | 5.992 | |
| 5.000 | 26.963 | |
| 25.000 | 2m 43s | |
| 100.000 | 10m 44s | |
| 1.000.000 | 1h 43m 3s | |
| 10.000.000 | 18h 29m 53s | |
| 12.974.336 | 24 hours * | |
| * by calculation | |
notes
- The highest server load measured was 1.92(!), so your surfers will never have to wait.
- The requests were made in sets of 2, so 1 million hits was 2 * 500.000 simultaneous requests.
By increasing the amount of simultaneous requests the performance will go up because modern-day
CPU's are great at dealing with multi-processes and queues
- The initializing and creating of a socket, and the connecting to the webserver was done from the
test-server itself. Normally this is done by the surfer. As a result, the results of the benchmarks
are slightly lower than when another server would have been used to make the requests.
- 100% of the hits were counted. Because ATX can work flawless with the disk cache, issues like
cache-overloading and file-locks will not be a problem anymore.
As you can see, ATX can handle approx 15 million hits per day easily on a default installation of FreeBSD
with a server load of around 2. Professional hosts usually optimize and fine-tune their (web)servers
to get anywhere from 0% to 200% more performance. Important is that you have plenty of RAM in your server,
(whether you're running ATX or not) to prevent the system from using your virtual memory.
If your websites generate numbers like 10 million hits per day , you will probably want to switch to a
faster webserver like Zeus Webserver which runs on some of the biggest sites
in the world.
|
trade-less stats overview
|
history stats
|
Site Compliance Spider
(keeping the bad guys out)
|
|
changing the style with css
|
add trade form with red style
|
add trade form with blue style
(AT Lite look-a-like)
|
|
outgoing settings empty
|
outgoing settings filled
|
search engine list
(total of ~150 domains)
|
|
Extra variables
|
All sorts of headers...
|
country stats for SE traffic
|
|
