Not to weaken the New Dev thread... but where do we want to go? So far we have tossed around notions of:
* Flexible storage - flatfiles, SQL, the current "log file gather" (slow, but reliable - if the log files aren't trashed)
* Supporting new projects - RC5-72 is comin' up. What tweaks we adding?
* More features/status? What needs adding?
okay, so there hasn't been alot of discussion about it... and i'm making up some of this (most) as I go. :)
If you wish to catch me for realtime chat I can be found in #perproxystats on irc.fxchat.net.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The storage/summary methods are an essential part of a new release IMO. It must run faster than 7.1. I've got a small list of bugs to be fixed too, along with general code tidy up. After that I think there are three areas to be worked on - here they are, along with some ideas for things TODO under each:
1) Continual improvement to how ppstats works
* Summary storage methods.
* More general framwork for everything.
* Tidy/rewrite HTML output. Make it look better, use CSS a bit better, standards compliant.
* Integration of the different contests (so only one script and config file is needed). Needs some of the generalisation work to allow each contest to define its own unit name (nodes/keys/etc) and so forth.
2) New Features
* By week/day/(hour?) stats. This is the kind of thing that would benefit from a generalised framework.
* Nicknames. To enable hiding of emails, or at least associate emails with IRC nicks/real names.
* Email retire function (I have an implementation of this against 7.1 if anyone's interested).
* User customisation. Slightly tricky as it requires using being able to authenticate on your website and some method to update details - may not be available to everyone. Users would be able to edit their displayed details, retire their own IDs, etc.
* "Hitparade" of top workers for today/last week/last month/ever.
3) Extra tools - small scripts or programs not strictly part of ppstats, but that might work off the same data, or are useful to someone running a proxy.
* Other methods of reporting the stats data. eg: a script for IRC bots.
* proxy monitoring of number of clients/units/etc. The data from this could be also be used to provide more stats which would be another item for 2)
That'll do for now. :)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Within I made some of the thinks working that we announced for Version 8.0 that stays in CVS for long time.
In the main part it is a Version 7.1 with MySQL support, it has build in "retire" support (needs to be done by the host manually). On thing I did not build in for now is the "up-down"-ranking.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Stuart, i'll let you look at that since you've got time at the moment. :) I gotta deal with some people taking a tour of our facility...
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
-
2002-10-21
I run a small network of machines, ranging between 10 (at the moment) and 25 (when I can get away with it and the wife isn't looking). They are all (obviously) crunching DNet packets, and using the same email address. For various reasons I run a PerProxy. I use this stats project to help me monitor them and see any clients which have died. This project is great!
The only thing that would make it greater would be some sort of Team/SingleUser flag, so that the links to the team pages could be links to the user pages etc.
I had considered making changes and submitting the modified files as a patch, when what happens, but RC5/64 finishes!
If you do consider this functionality, I'd be happy to test it.
Would the proposed DBMS support be optional or mandatory?
Now, all I've got to do is work out how to tell SF to let me know when there are new postings to this thread.
Thanks guys,
Carl
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Some thinking certainly needs to be done about how to build the actual HTML output to make it so doing what you want would be easier. Tidying this up and making ppstats produce stuff that's easier to fit into existing templates is certainly planned.
With regards to RDMS support, my view on this is that it should definitely be optional. You should be able to choose between storing the compressed data in flat textfiles, or some kind of DB (adding support for alternatives would just require implementing necessary functions calls).
Sorry for the lack of updates - had various things going on, but it's all settling down now. I have been working on some code, and I hope to start making this available, and doing regular updates from next week when I'm back on broadband at home. The plan is to rough out how I think the core information-storage system (for want of a better description) should work, and publish some docs on it for people to review and comment on. After that we can release a 8.0 version with this, and some bug fixes and tidy ups, and then work in earnest on 8.1 which will improve the look of things and add features utilising the new functionality.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I used to use ppstats 7.1 (for RC5-64) on my network and am now hoping that something can be done towards rc5-72 and improving what we already have (especially speed, a year of rc5 on my old pentium takes about 5-10 mins to complete)
I'm glad to here that some thoughts are being put together to further developing 8.0, and I'd like to help if possible.
One thing I think should be included is some sort of configuration (or have I missed this) such that the generation of stats by day/week etc could be disabled/enabled as the operator wishes.
Whilst this is in development, could perhaps a 7.2 'formal' issue be done with effectively rc5-64 replaced by rc5-72 and a few tweaks where the proxy output format has changed (if at all).
Cheers
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I made a quick hack (everything was very easy) and tested the version 7.1 with RC5-72. It looks good, only the links to the statistics are not changed, they are still pointing back to the RC5-62 project.
Not to weaken the New Dev thread... but where do we want to go? So far we have tossed around notions of:
* Flexible storage - flatfiles, SQL, the current "log file gather" (slow, but reliable - if the log files aren't trashed)
* Supporting new projects - RC5-72 is comin' up. What tweaks we adding?
* More features/status? What needs adding?
okay, so there hasn't been alot of discussion about it... and i'm making up some of this (most) as I go. :)
If you wish to catch me for realtime chat I can be found in #perproxystats on irc.fxchat.net.
The storage/summary methods are an essential part of a new release IMO. It must run faster than 7.1. I've got a small list of bugs to be fixed too, along with general code tidy up. After that I think there are three areas to be worked on - here they are, along with some ideas for things TODO under each:
1) Continual improvement to how ppstats works
* Summary storage methods.
* More general framwork for everything.
* Tidy/rewrite HTML output. Make it look better, use CSS a bit better, standards compliant.
* Integration of the different contests (so only one script and config file is needed). Needs some of the generalisation work to allow each contest to define its own unit name (nodes/keys/etc) and so forth.
2) New Features
* By week/day/(hour?) stats. This is the kind of thing that would benefit from a generalised framework.
* Nicknames. To enable hiding of emails, or at least associate emails with IRC nicks/real names.
* Email retire function (I have an implementation of this against 7.1 if anyone's interested).
* User customisation. Slightly tricky as it requires using being able to authenticate on your website and some method to update details - may not be available to everyone. Users would be able to edit their displayed details, retire their own IDs, etc.
* "Hitparade" of top workers for today/last week/last month/ever.
3) Extra tools - small scripts or programs not strictly part of ppstats, but that might work off the same data, or are useful to someone running a proxy.
* Other methods of reporting the stats data. eg: a script for IRC bots.
* proxy monitoring of number of clients/units/etc. The data from this could be also be used to provide more stats which would be another item for 2)
That'll do for now. :)
As I sad before, take a look at the code in this file: http://www.intrepid.de/ppstats/ppstats-8.1-alpha-5.tar.gz
Within I made some of the thinks working that we announced for Version 8.0 that stays in CVS for long time.
In the main part it is a Version 7.1 with MySQL support, it has build in "retire" support (needs to be done by the host manually). On thing I did not build in for now is the "up-down"-ranking.
Stuart, i'll let you look at that since you've got time at the moment. :) I gotta deal with some people taking a tour of our facility...
I run a small network of machines, ranging between 10 (at the moment) and 25 (when I can get away with it and the wife isn't looking). They are all (obviously) crunching DNet packets, and using the same email address. For various reasons I run a PerProxy. I use this stats project to help me monitor them and see any clients which have died. This project is great!
The only thing that would make it greater would be some sort of Team/SingleUser flag, so that the links to the team pages could be links to the user pages etc.
I had considered making changes and submitting the modified files as a patch, when what happens, but RC5/64 finishes!
If you do consider this functionality, I'd be happy to test it.
Would the proposed DBMS support be optional or mandatory?
Now, all I've got to do is work out how to tell SF to let me know when there are new postings to this thread.
Thanks guys,
Carl
Hiya
Some thinking certainly needs to be done about how to build the actual HTML output to make it so doing what you want would be easier. Tidying this up and making ppstats produce stuff that's easier to fit into existing templates is certainly planned.
With regards to RDMS support, my view on this is that it should definitely be optional. You should be able to choose between storing the compressed data in flat textfiles, or some kind of DB (adding support for alternatives would just require implementing necessary functions calls).
Sorry for the lack of updates - had various things going on, but it's all settling down now. I have been working on some code, and I hope to start making this available, and doing regular updates from next week when I'm back on broadband at home. The plan is to rough out how I think the core information-storage system (for want of a better description) should work, and publish some docs on it for people to review and comment on. After that we can release a 8.0 version with this, and some bug fixes and tidy ups, and then work in earnest on 8.1 which will improve the look of things and add features utilising the new functionality.
I used to use ppstats 7.1 (for RC5-64) on my network and am now hoping that something can be done towards rc5-72 and improving what we already have (especially speed, a year of rc5 on my old pentium takes about 5-10 mins to complete)
I'm glad to here that some thoughts are being put together to further developing 8.0, and I'd like to help if possible.
One thing I think should be included is some sort of configuration (or have I missed this) such that the generation of stats by day/week etc could be disabled/enabled as the operator wishes.
Whilst this is in development, could perhaps a 7.2 'formal' issue be done with effectively rc5-64 replaced by rc5-72 and a few tweaks where the proxy output format has changed (if at all).
Cheers
Hi Mark (standardeight),
I made a quick hack (everything was very easy) and tested the version 7.1 with RC5-72. It looks good, only the links to the statistics are not changed, they are still pointing back to the RC5-62 project.
You (and everyone else) can find it at http://www.intrepid.de/ppstats/ppstats-rc572-7.1-png.tar.gz
I will send this version to Gerald just after I finished this message, so it will maybe on this site someday.
Regards
Oliver Fabender