perfidix-users

[Perfidix-users] Perclipse 2.0 released

[Sebastian G. <seb...@un...>]

Hello everybody (again),

After the Release of Perfidix 3.4 we have updated Perclipse (our  
Perfidix-Eclipse-Frontent) as well. New features of Perclipse 2.0 are:

- Full PMD-Check
- Complete configurable of all perfidix-features (runs, gc- 
probability, listeners, ...)
- Progess bar and on-time information of the current bench

For more information, please refer perfidix.org. The updatesite for  
direct installation is available over http://perfidix.disy.inf.uni-konstanz.de/updateSite 
  .

greetings

sebastian


--------------------------------------------------
Sebastian Graf
Distributed Systems Group
Department of Computer and Information Science
University of Konstanz
Phone: +49 7531 88 4319
Mail: seb...@un...

[Perfidix-users] Perfidix 3.4 released

[Sebastian G. <seb...@un...>]

Hello everybody,

today, we released Perfidix 3.4 as the new backend for the upcoming  
Perclipse (Perfidix-Eclipse) Plugin. The following features are:

- Full PMD-Check
- Socket-Connection as a base for third-party applications
- Configuration through the classpath of all features.

For more information and downloads refer to the updated documentation  
at perfidix.org and stay tuned for the new Perclipse-Plugin.

greetings

sebastian


--------------------------------------------------
Sebastian Graf
Distributed Systems Group
Department of Computer and Information Science
University of Konstanz
Phone: +49 7531 88 4319
Mail: seb...@un...

[Perfidix-users] Current status and further developement

[Sebastian G. <seb...@un...>]

Hello everybody,

because of backup conveniences I would prefer english for  
communicating on the maillists.

At the momentan, perfidix 2.4 is released (and stored in the  
repository, but not yet in the download section on the sourceforge  
site) with the following changes:
- virtual memory tracking of a benchrun
- meter debugging
- raw output for csv-raw data (not the result)

In the near future, perfidix is going to be moved to maven including  
new src structure ensuring a better and much more stable build  
process. The next steps are including checkstyle, refactoring and  
cleaning up the code. Then the features already submitted in the  
sourceforge tracker are going to be implemented.

If you find any bugs or if you have any suggestions for further  
developement or if you know someone to join the developer team, don't  
hesitate to submit into the tracker or/and to contact me.

greetings

sebastian