If I set the IN path to my network drive - it unpacks from network
drive back to network drive, then processes TOSS from network drive - basically triple+ my billable. (Running VPS servers with BandWidth Quotas)...
If I set the IN path to my network drive - it unpacks from network
drive back to network drive, then processes TOSS from network drive - basically triple+ my billable. (Running VPS servers with BandWidth Quotas)...
Can we add UNPACK TO PATH?
Hi Ozz,
On 2019-02-08 23:06:00, you wrote to All:
Can we add UNPACK TO PATH?
You mean something like a TEMP path where it puts "inbetween" files?
My uplink sends compressed, which to make makes much more sense then compress on the fly (personal preference).
Hi Ozz,
On 2019-02-14 10:23:58, you wrote to me:
Current fidonet over the internet, is so fast, that most sessions only exchange a single pkt file, with only a single or a few messages, typically a few hundreds or thousands bytes. It makes no sense
starting up a compression program, that writes them to an compressed "intermediate" file on disk before transmission, when most of those
pkt files fit into a single tcp/ip frame. Or when binkp can compress
them on the fly which doesn't require extra disk writes and reads for
the compressed data.
Current fidonet over the internet, is so fast, that most sessions
only exchange a single pkt file, with only a single or a few
messages, typically a few hundreds or thousands bytes. It makes no
sense starting up a compression program, that writes them to an
compressed "intermediate" file on disk before transmission, when most
of those pkt files fit into a single tcp/ip frame. Or when binkp can
compress them on the fly which doesn't require extra disk writes and
reads for the compressed data.
True for Fidonet - however, other networks I am on push hundreds of messages per poll. But, I only poll them 2 or 3 times a day - and they are extremely active. No problem.
True for Fidonet - however, other networks I am on push hundreds of messages per poll. But, I only poll them 2 or 3 times a day - and they are extremely active. No problem.
my new setup processes the mail and files as soon as they come in... "WOW!" doesn't even begin to cover the experiance of seeing messages
come in, being fully processed, and sent out to all my linked systems
in less than 30 seconds...
That's a use-case where compression makes sense. So it's a good thing
you can choose for each connection if you want compression or not! ;)
No complaints here! I am honestly impressed in how well FMail is
operating in my mailer in Virginia, Tosser in Texas, NNTP Server in
Texas, and NNTP Client on my Mac Laptop in Virginia ;-)
my new setup processes the mail and files as soon as they come in...
"WOW!" doesn't even begin to cover the experiance of seeing messages
come in, being fully processed, and sent out to all my linked systems
in less than 30 seconds...
That's slow! ;)
imagine what it'll be like when you get a """real setup""" going (J/K!)
where you are in a "crash me, crash you" configuration such that pkts
and tics/files are processed immediately on arrival... my old system
used to process mail once an hour before it became a tier 1 mail hub...
it spent a lot of time processing mail... especially since it was also
only 800Mhz... my new setup processes the mail and files as soon as
they come in... "WOW!" doesn't even begin to cover the experiance of
seeing messages come in, being fully processed, and sent out to all my
linked systems in less than 30 seconds... i have some stats around here somewhere that i need to figure out how to process and look at in a
more human readable format...
| Sysop: | digital man |
|---|---|
| Location: | Riverside County, California |
| Users: | 1,065 |
| Nodes: | 17 (1 / 16) |
| Uptime: | 22:34:07 |
| Calls: | 501,328 |
| Calls today: | 7 |
| Files: | 109,413 |
| D/L today: |
6,134 files (632M bytes) |
| Messages: | 302,051 |