-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 В Вт, 19/02/2019 в 11:58 +0100, Armin Novak via FreeRDP-devel пишет: > Hi, > > > Yes, the pooling could require some fine tuning (and specially the > channels could reduce the number of threads used) > > As you already recognized, we mainly use it with 1 connection, but > per > context. Every context managing resources on its own. > > > To answer your question, yes, we´re always interested in patches that > can bring down overall resource usage and enhance configurability. > > Might not be everything you´ve done (if it is too specific) but > especially threading and event management could be interesting. > > > regards > > Armin > > > On 2/19/19 11:20 AM, Alexandr via FreeRDP-devel wrote: > > Currently freerdp designed in a way which does not allow to use it > > efficiently with high number of outgoing connections, looks like it > > designed for one connection per process/app. > > This is not what we need in our application. we need to manage all > > resources internally in our app, and have a lot of outgoing > > connections, to achieve this freerdp must be redesigned. > > 1. libfreerdp core need option to disable internal thread pool and > > other resource managing (this is possible with small code edits, > > already done inside our app). > > of course more improvements for event based workload balancing can > > be > > done. > > 2. addins. currently addins creating per connection threads with > > internal loops, this is sub-optimal and also causing stability > > issues, > > unfortunately it can't be easily turned off and require some > > redesign > > of each addin internals, also can be an option (or some global > > options > > to disable internal resource managing) > > we have not done anything with addins yet. > > > > so my question: > > Does freerdp devs interested at all in adding apis for high load > > apps > > in freerdp/libfreerdp ? > > if so, we can implement this for merging with upstream. > > > > > _______________________________________________ > FreeRDP- > > > > > devel > mailing list > FreeRDP-devel@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/freerdp-devel > > > > _______________________________________________ > FreeRDP-devel mailing list > FreeRDP-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freerdp-devel
thx for reply. pleasure to know this. so i will prepare optional support for single thread event-based mode for libfreerdp and addins to be used with external thread pool and/or event library for merging with upstream. i think rdpSettings is proper place to put setting in, also i will redesign some internals to do all polling in one place (libfreerdp or external event library), this will most probably introduce some new apis for addins. -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEEWlDDCYMF8IYr2FvNCBybLMY3dFAFAlxr55UACgkQCBybLMY3 dFB9Ag//QH34vrGyb7rVM6wnQsS6m3Gaqg9HXL1+W2/8VhKjfMGyoaiY25t33kJK tpJFizpNyfDNcC+SL5aCe6zcnJ8FuuwNrDyNZo3TXnOl6DsekYgyKACRck9RGbwL zlRMGSXEYZEnzgGSeSkuUg/BJkajPlMx5M1BCnZGVPUujQ//o/TPTvIzIPDr5aDI iBTKUnNMI0vw1ftaYok7XjZ0QdTtlqdu9vyzgTLCkrygy6JZdSGG3o4lC0sRhoMP jEoj7ljtM+BjQGROrt+zrNXTfER9NEdvC47DG/lp5mUfzw7a5ho//cqGoqRxqmo3 QhvkU7+SeOWF9ibJjHTcBNrH91zmm89MgKh2h5p3Ll9VEzeLSOxx99P4GfgRDEVq exh7pi/A3cJDUbmflBJsK+AGdQ+hAhQFJkm2LF0lCk7woTo/FtYHQXOPxQBrnzzZ eQgtxe6xZzw40XbMrdo8GdE22hL3CFk2So2HBzv2FOEZrQ2qbhq0OCo2IQMzuBPd Desw4qRF/eG50rslZAb8mXV7H3O6Q0CSPD2OO8lgSqCqU8cbcHp2ZNvFmPtRVegs GG5hbz/mqKXVW+UmbxpUEJHtTSEv7zF0cCfZfbl5tLuvbFmVClJYSc4U5fxHjkpf Bj0TdXK7yJ7tcxD/fVN9PyG0am9H3N9FXLlgpkCBBTI9TAYgZL8= =EI51 -----END PGP SIGNATURE----- _______________________________________________ FreeRDP-devel mailing list FreeRDP-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freerdp-devel
