search attempt settings

[Pirre]

strgdc do's not respect the search setting interval nor the tth interval when adding new files to Q, it reaches rates as high as 30/min when hub/client connection is fast enough with adding 40 files

[Big Muscle (bigmuscle)]

When you add files into queue, StrongDC++ puts them immediately into search queue. It means that search request is sent to hub in intervals you have set for your favorite hub (or global settings when 0). For example, if you add 30 files into your queue and your search interval is set to default (i.e. 10 seconds), then 30 search requests will be sent to hub with 10 second delay between each one.

[Pirre (pierreparys)]

Yes thats what i understould before from your previous explenation, i use the defaults settings in both places (in favs and settings) whats 15 seconds.

When i add 30 files in my Q i reach rates above 20 a minute and thats far above the 1 in 15 seconds and i am pritty sure if i add a 100 its like a machinegun lol :)

It seems that it sends the nxt search before its aware of all those done before :)

ps: same counts for that max simultane dl's setting also there it seems not aware of dl slots taken if you select for example 30 lists to dl.

[Big Muscle (bigmuscle)]

Could you provide log from CDM window? What version do you use?

[Pirre (pierreparys)]

@ this moment like any good user a 2.42 :) but 2.41 did same

the cdm window doe not give time interval so going to give you a rate calculation from 1 hub Q' ing 15 files

Counter: 3 Avg.Rate: 7.059 / m Max.Rate: 7.059 / m thats on first 3 attempts then it slows down very fast.

Its like the first bunch of searches are gone before the limmit kicks in

this is with those 15 seconds setting and a tth auto search interval of 30 minutes

[endator (endator)]

for quite a while sdc has sent the first search directly when adding new items to the queue, it does not wait until the search interval is up, and this search is not logged in syslog. I do believe that remaining files is added to the search queue correctly though. (not clocked it, but searches listed in the syslog shows a reasonable interval).

[Pirre (pierreparys)]

not only are they not in syslog , as far i can see also exluded in nmdc window for some strange reason.

And after that having those autosearches limmited by a max rate setting is nice but if after they are added and become normall auto search the tth searches still dont obey that rule, they just keep beeing send @ max search rate, and its a stress.

[Big Muscle (bigmuscle)]

Marking as incomplete until more information is added. I tested every possible case and search interval was always respected.