* Jan Klod <janklodvan@xxxxxxxxx> wrote: > It might be, I gave too little information, so I'd appreciate some > questions or ready-usable advices! On a general note for cases like this: Look at it like you want to reproduce the problem yourself only with the info you provided. (read: If unsure, look at it from the viewpoint of a complete stranger who doesn't know what you are talking about; now exactly a numbnuts walkthrough, but you get the idea) > Apparently slow disk IO is the problem, but it IS caused by > particular programs, which could possibly have much lower priority. > It is terribly high now... I don't think this is loop-AES related. You could start resource-hogging applications with a nice level of 10 or somesuch and see if it affects things positively. > Have you experienced too slow reaction on session locking requests? > What did you do? Now you talk about session locking requests... In context of video playback, the first thing that comes to mind is a bad video file; borked index. Whatever file you want to play, open & save it in avidemux first to check its integrity. It also could be a codec issue (namely mp4 & mov, wmv occasionally). Such overwhelming lagging happened to me and it was due to low memory - perfectly reproduceable: fire up KDE, open a large pdf (2/3 of total RAM is sufficient), and start a text-search... eventually the system's OOM killer strikes, after a prelude of minutes in which the system is unresponsive/lagging at best. I'm still using a laptop with only half a gig of RAM. HTH a bit ... -- left blank, right bald loop-AES FAQ: http://mareichelt.de/pub/texts.loop-aes.php
Attachment:
pgpxaMDyr49jb.pgp
Description: PGP signature
