All Blocks Resized + Lost All Connections
-
Hi,
I'm afraid the problem persists. I was about to finish a project and suddenly the size of the blocks changed and returned to default settings T.TThanks in advance for following up.
Update:
I also noticed that all the information on the "Project Options" section has been deleted as well. -
Hi roar, Yes you are right, there is plenty of scope for improvement and de-duplication of blocks. I'm getting better each project but also this is quite a large project in it's own right. fxdreema has confirmed it was a temporary change whilst testing the above issues and all is back to normal again today.
And Yes, I do accept your challenge . . .
Thanks
-
@fxDreema Excellent work. Thanks for taking care of us.
-
Yes @Karlo1991 I agree, the problem still exists.
Blocks have gone blank, connections lost, constants and variables deleted again for me too.
Has happened 4-5 times in last few days - so far History has fixed it, so only lose a few blocks to restore.
Scary though, because before @fxDreema did his thing with the email logins to speed things up, once lost info, project was lost forever.
There is definitely a problem somewhere still, but I have faith that @fxDreema will find a solution soon
Until then, I suggest exporting mq5 file regularly as a back-up in case history doesn't resurrect lost info... -
Hey @fxDreema I might have noticed a pattern just before all the blocks disappear etc. No sure if it will help you but...
Often one of two error messages appear just before the crash - one says "There is a problem with the block you are trying to move, reloading might fix the problem" or "There is no connection to the website at the moment. Please try again later."
I have rarely seen these messages prior to a couple of weeks ago - approximately coinciding with when these project crashes started. I have not changed internet setup so might be something about data saving to site? I don't know anything about it.
The crashes are getting frequent and really annoying.
I hope this might give you a clue to help track down what is going wrong.
Cheers,
Jim -
@Jim67, I'm not that surprized of the fact that sometimes projects are breaking, because this is not something new, it always happened. I must agree that the process of saving the project's current state it not very well polished. Basically, when you do some action (new block, blocks move, connection), everything in the browser (blocks, connections, areas) is read and sent to the server for saving. Ideally, what you see in the browser matches the records on the server. The problem is that if there is some mismatch, the project could break. And such mismatches could happen when there are problems with the communication between the browser and the server. I'm in a process of rewriting the whole website and eventually I will add different guardrails to prevent projects from breaking, but at this time projects are sometimes fragile.
My concern is when there are problems with the communication with the server. I'm still noticing slow moments from time to time. Not as bad as it was days ago, but still noticeable.
Otherwise I can suggest to reload the project more often. Personally I never experienced that moment when a project breaks, maybe because every time when something doesn't look right to me, I realod the whole page. But I probably do this because I know how a project could break.
-
Ok @fxDreema thanks for your explanation - will do same and reload regularly.
It's definitely been quicker and better since your first fix with that email thingy.
And great to hear you're onto trying to solve the breaking problem.
You're a prince among men
-
I found yet another slow query. Well, this one is not always slow, it becomes slow when the user has 1000s of projects, because there is sorting involved, which takes few seconds. And all of this is to get just the id of the last modified project. But it's possible to make this query very fast, I'm now trying to see exactly how. At this point it should be obvious that I'm not very good with databases
-
Ok @fxDreema - So if I delete my old unused projects that should help?
-- because I do have alot of old projects - not 100's buy probably 100.
I'll delete them anyway I think
Thanks again for getting onto this mate -
@Jim67, almost nothing will change if you delete your ~100 projects.
The problem I'm investigating now happens (I believe) when somebody with 1000s of projects is creating a new project. Although the exact way the problem happens doesn't really matter. Normal accounts are like yours - not 1000s of projects, not 1000s of blocks in their projects. But there are these students of the guy that I mentioned before that have the 1000s of projects and some of them have projects with 1000s of blocks. When they are active during the day, they are "benchmarking" the website. Because of the way these guys are using the website, those slow database queries are showing up.
But the slow database queries are slow, because they are not properly optimized. In databases there is something called "index", which is when part of the database is cached in the RAM and is used for quick searches. Well, what I'm discovering these days is that some of the queries I wrote are not using the indexes effectively. If everything is well optimized, those 1000s of blocks should be no problem at all and the queries should happen in just a few milliseconds. Because they are not optimized now, they happen in few seconds.
But again, these are just a few queries that just a few accounts are "abusing". Why everyone experiences slow moments is that while the database is processing these slow queries, the other queries are waiting.
-
Ahh OK I see @fxDreema - I deleted about 100 of my projects anyway, hoping it might help.
So why not just put a project / block limit on these greedy pricks that are causing problems for everyone else.
It's your site after all, you call the shots - 99% of users would support you I reckon.Thanks again for the explanation.
-
@Jim67 there is a limit already
-
Oh OK @roar - I was just trying to help - maybe reduce the limits then.
I dunno -
@roar Let's say that the middle number on the right side is there only to scare people. The real number at the moment is 8000
@Jim67 I used the word "abusing", because with it I think it's easier to understand. But note that the word is in quotes, so I don't mean it literally.
I tried to explain this few times and I will say it again - the database is slow, because my code and the database indexes that I created are not very well optimized. This is because I don't have a good knowledge of databases. Not to mention that the deletion of old projects is just annoying, so no wonder why these guys have 1000s of projects. But that "abuse" is actually helping in a way, because it shows me where I need to fix the performance. While I'm doing that I'm also learning more about the database, which will be useful in future.
By the way, in the very beginning when I launched the website, projects were already too heavy with just 50 blocks.
If the code and the database indexes are well optimized, the server can handle those 1000s of projects and 1000s of blocks. Well, if the number of users grows, at some point other kind of optimizations will be required and I will have to learn more about databases, but we are not there yet.
-
Meanwhile an hour ago I updated all database queries. My hope and expectation now is that the website will be a little bit more stable when the 1000s of projects and 1000s of blocks come tomorrow.
-
@fxDreema
Everytime you talk about the 1000 blocks, I raise a question to myself: is it a joke? -
All good @fxDreema - I was being flippant really anyway
I hope your database tweaks help.
Onward and upward chaps
