performance of Pligg + karma integration

[dollars5]

Hi,

I would really liked to know the performance of Pligg in the following terms:
1] number of queries per page display (is it possible to see it in html as we have in wordpress)
2] why is Pligg kinda slow - is it fully attributed to Smarty and is it possible to get rid of it?
3] I [plan to display Karma of each user next to his name (where ever it gets displayed) - so is calls to karma gonna have an overhead in terms of DB calls? if so how many calls does it make?
4] Any good pointers on Karma module tweaking for my requirement as stated above?
5] Is any db calls optimization possible further on Pligg as a whole?

Thanks and looking forward for your answers.

[savant]

1. you can open /lib/db.php and set $debug_all = true

2. Pligg is slow the first time as it needs to compile the .tpl files into php files. After that the script is a bit quicker. Applications like Pligg is very data intensive so you do need a nice server and database. pliggers have brought new ideas like using gzip to compress the js and css files.

3. The karma value is part of the User Data. /libs/user.php so you can create a new user object and use the method read(). and display $user->karma.
This is OOP method and will get all the information about the user from just the database. Select * from table where username= "Something" will take longer than select karma from table where username="something". So you will need to find out whether OOP or Procedural is better for you.

4. As far as i know there isn't much on karma atm. Best let KB or Ash answer this.

5. We are open to suggestions. If you can find better methods please do post.

[dollars5]

Thanks savant for your quick reply.

1. Worked great and gave me some idea.

2. So slowness of Pligg doesn't have anything to do with Smarty Engine? I was assuming Smarty causes the slowness.

3. ur suggestion on Karma worked and thanks

4. waiting for ashDigg or KB answer this.

5. me still sxploring the world of Pligg, once I get more familiar - sure I would pour in with suggestions and code contributions :)

[savant]

2. It's using template lite which is smarty lite. and yes templating is one of the reasons the site is a bit slow. But with proper caching and performance enhancements i'm sure pligg can be made better.

[Adaman]

I do not know if this will be of any use to this thread but i was reading a nice litle article on smarty template cache, you can see it below.

http://alexander.kirk.at/papers/cach...thesisch9.html

Adam

[dollars5]

Very Good read Adaman. We should get some lead devs of Pligg to read this too - optimization and speedup is a major issue for pligg as I see, rather than adding more features which will further slow down the system.

The reason I was worried on db was many hosts have a slower server for their db systems and each call will take say n seconds and if Pligg takes say m such calls the total delay in rendering the page is gonna be (m X n) seconds which is very significant. By grouping many database and reading only critical data needed we can optimize in this part - just my suggestion.

Will review the pligg db access and db structures and will come up with pin-pointed suggestions - sooner.

[AshDigg]

We have been working on caching and have been having some troubles but we're still working on it. :)

[dollars5]

Good to hear that from you AshDigg.

We are also eager to help you out in this area. Our company works mainly into mobile and now entered into social networking development too - I can get our Web development team to work closely with you on making Pligg better (it is already better compared to many other things)

Thanks and Regards.
dollars5
http://www.dollars5.com/plete

[savant]

thats great dollars5. the more the merrier. :)