ramblin rose
Member of DD Central
“Some people grumble that roses have thorns; I am grateful that thorns have roses.” — Alphonse Karr
Posts: 1,370
Likes: 857
|
Post by ramblin rose on Feb 20, 2017 19:03:31 GMT
Perhaps it's unreasonable of me to expect the sales process to work quickly and efficiently when there are people with buy orders clearly in place and waiting to spend their spondooliks? I put in a small sell order early in the afternoon today on a loan that I know there are people waiting to buy; it took till the end of the afternoon for the clever-clogs algorithm to plod its way around and actually sell it to them. Perhaps I'm the only sad person left on the platform who cares about such things. This infrastructure strikes me as getting a bit creaky, and as a soon-to-be shareholder I'm not all that impressed with it. I've always thought the new all-singing, all-dancing software we got presented with whenever it was ago was too complicated for its own good, and I'm not being convinced otherwise as time creaks by.
Sigh.
|
|
investibod
Member of DD Central
Posts: 288
Likes: 152
|
Post by investibod on Feb 20, 2017 19:56:02 GMT
I believe that Chris (in the good old days when he used to post here) said that the algorithm cycled through the loans about every 2 hours. So if it had just passed the loan you were trying to sell, it would be about 2 hours before it visited it again. Does that reflect the sort of time-scale you were seeing?
|
|
|
Post by yorkshireman on Feb 20, 2017 21:09:16 GMT
I care about such things! Unfortunately this seems to have become the norm, I’ve never actually timed it but based on recent experience I would say that it takes longer than 2 hours.
|
|
ramblin rose
Member of DD Central
“Some people grumble that roses have thorns; I am grateful that thorns have roses.” — Alphonse Karr
Posts: 1,370
Likes: 857
|
Post by ramblin rose on Feb 21, 2017 9:42:44 GMT
I believe that Chris (in the good old days when he used to post here) said that the algorithm cycled through the loans about every 2 hours. So if it had just passed the loan you were trying to sell, it would be about 2 hours before it visited it again. Does that reflect the sort of time-scale you were seeing? No, it was more like 4 hours I'm afraid - I didn't pay precise attention to the time but it was all afternoon and definitely way more than 2. I've mentioned it because I've noticed a real deterioration recently - I regularly sell small chunks to keep the shrapnellator fed.
|
|
Investboy
Member of DD Central
Trying to recover from P2P revolution
Posts: 564
Likes: 201
|
Post by Investboy on Feb 21, 2017 15:08:18 GMT
I just went through major sell exercise and must say I'm impressed. I don't care about 3 or 4 hours. All loans sold withing 1 day.
|
|
iren
Member of DD Central
Posts: 302
Likes: 300
|
Post by iren on Feb 22, 2017 1:11:58 GMT
The other increasing delay is the gap between a capital repayment showing on the MLIA statement, and the adjustment to capital being reflected on the Your Loans page e.g. case in point loan 283, repayment credited 21 Feb 16:41, still not yet reflected on Your Loans at 22 Feb 01:10.
|
|
tonyr
Member of DD Central
Posts: 477
Likes: 258
|
Post by tonyr on Feb 22, 2017 1:30:57 GMT
I would like a much faster turn around. I still remember the day when I put an extra zero into the sell field by mistake and clocked okay - my hard earned investment was gone before I could do anything about it.
I wonder if the delay is not intentional (it's about 2am now and not much is happening, including my buy/sell orders). There's a great book called Flash Boys where they deliberately introduced a trading delay to make things fair. There are API users now.
|
|
|
Post by lynnanthony on Feb 22, 2017 8:49:50 GMT
The other increasing delay is the gap between a capital repayment showing on the MLIA statement, and the adjustment to capital being reflected on the Your Loans page e.g. case in point loan 283, repayment credited 21 Feb 16:41, still not yet reflected on Your Loans at 22 Feb 01:10. Yes I had noticed that, and I don't really understand why the two places cannot be updated simultaneously.
|
|
sl75
Posts: 2,092
Likes: 1,245
|
Post by sl75 on Feb 22, 2017 10:37:33 GMT
I think it's partly do to The Algorithm being so riddled with bugs that the only way they can stop the system completely melting down is to throttle it to only be allowed to consider each loan once every few hours.
In the past, we've seen examples of faults in The Algorithm such as: - using only 98.01% of available cash when buying a loan at a 1% discount (then the next time the loan is processed, using 98.01% of what's left, and so on, until the remaining 1.99% is so small as to be below the minimum representable currency unit). - repeatedly buying and selling the same loan via investment accounts.
By slowing it down so much, the effects of such bugs are largely masked - several hours later the conditions will probably have changed sufficiently that the next transaction in the anomolous series is no longer possible and/or desireable.
In principle, The Algorithm should be fairly straightforward to verify - given a current database state and a loanId to process, it should either report (correctly) that no trades are possible for that loan Id, or generate a complete list of transactions that fully exhausts all possible trades (so if that transaction list is processed, and no other actions are performed that change the database state as it pertains to that loan, the resulting database state would have no trades possible in that loan Id).
Some of the visible side-effects of current faults in The Algorithm include: - several loans at any given moment with "<£0.00" available. A single loan could occur by co-incidence on rare occasions, as the last buyer left less than a penny of the amount offered for sale. Multiple loans suggests instead that it is The Algorithm at fault. - significant numbers of transactions of tiny fractions of a penny. Again this might occasionally happen in "genuine" circumstances, but more often indicates a problem where The Algorithm left behind some shrapnel that it has to clean up the next time it processes that loan. - an investment accounts (including MLIA) being left with a tiny fractional amount uninvested more than very occasionally [unless this occurs by design with a later redesign of The Algorithm - such as to increase the implicit 'share price' for loans so that it is above rather than below the smallest representable currency unit].
|
|
iren
Member of DD Central
Posts: 302
Likes: 300
|
Post by iren on Feb 22, 2017 14:37:08 GMT
The other increasing delay is the gap between a capital repayment showing on the MLIA statement, and the adjustment to capital being reflected on the Your Loans page e.g. case in point loan 283, repayment credited 21 Feb 16:41, still not yet reflected on Your Loans at 22 Feb 01:10. Yes I had noticed that, and I don't really understand why the two places cannot be updated simultaneously. The issue causes two problems for me: -The account is overvalued on the dashboard for a period, while the same funds are counted as cash and as an amount on loan. This creates an anomaly when I'm doing my own reconciliation. -It complicates the process of adjusting my buy target to reflect the repayment. I expect sl75 is correct about the issues with the algorithm.
|
|
|
Post by lynnanthony on Feb 23, 2017 8:51:23 GMT
The other increasing delay is the gap between a capital repayment showing on the MLIA statement, and the adjustment to capital being reflected on the Your Loans page e.g. case in point loan 283, repayment credited 21 Feb 16:41, still not yet reflected on Your Loans at 22 Feb 01:10. Loan 106. I had principal credited at 16:56 on 22nd. As at 08:49 on 23rd my loan book has still not caught up. Something ain't working.
|
|
sqh
Member of DD Central
Before P2P, savers put a guinea in a piggy bank, now they smash the banks to become guinea pigs.
Posts: 1,428
Likes: 1,212
|
Post by sqh on Mar 21, 2017 6:29:15 GMT
Early this morning I made a sale that has generated 1859 entries in my statement summary. Then another 1859 entries as each entry was swept into the qaa. That's over 74 pages for one sale. Nearly all the entries are 0.00000000000000000002.
It's no wonder the time to sell appears to have increased.
|
|
|
Post by lynnanthony on Mar 21, 2017 7:53:32 GMT
Early this morning I made a sale that has generated 1859 entries in my statement summary. Then another 1859 entries as each entry was swept into the qaa. That's over 74 pages for one sale. Nearly all the entries are 0.00000000000000000002. It's no wonder the time to sell appears to have increased. Is it purely my imagination, or was the original proposal for the shrapnelator to have a minimum unit size? A pound I seem to remember? With just one unit of each sale being less than a pound to clear the end bit of any sale. So if say £100 of a loan was offered and there were 150 buyers interested, 100 lucky buyers would be picked at random.
|
|
oldgrumpy
Member of DD Central
Posts: 5,087
Likes: 3,233
|
Post by oldgrumpy on Mar 21, 2017 11:32:41 GMT
Early this morning I made a sale that has generated 1859 entries in my statement summary. Then another 1859 entries as each entry was swept into the qaa. That's over 74 pages for one sale. Nearly all the entries are 0.00000000000000000002. It's no wonder the time to sell appears to have increased. It is nonsense that we are still presented with this kind of extreme bloat. I detest the time wasting I have to do when checking for specific loan part sales in my statement. chris Can something be done avoid this, please? When I sell, all I need to know is how much has been sold (or bought). I don't need to know how many different people bought it, thank you. I won't be checking whether one of my £0.00000000000000000002s is missing or even whether one of the noughts is missing ... (unless it is a nought at the end of the whole pounds column ) 74 pages??? Rats to that!
|
|
oldgrumpy
Member of DD Central
Posts: 5,087
Likes: 3,233
|
Post by oldgrumpy on Mar 21, 2017 13:29:01 GMT
I just found that hovering the cursor over the "invest" word at the bottom of the black box brings up just the most recent (total) transaction (bought or sold) but doesn't say when. Is that where you mean? That function is hidden away without instructions anywhere from AC, it seems to me. *edit - no need to wink (to avoid offending me) ... I am simple!
|
|