Why does memory keep increasing during training? about generative_mlzsl

[dgbarclay]

Likewise, trying to find a fix now.

My process keeps getting killed, even when running with 25GB RAM on Google Colab.

[dgbarclay]

@hugh920 could you let me know if you find a fix in the meantime 👍

[hugh920]

@dgbarclay When you train, does your memory increase with each epoch?How many epochs have you reached so far?

[dgbarclay]

@hugh920 Mine is being killed whilst parsing the data, it doesn't reach the beginning of training. It seems to fall within the block on line 203 of util.py. Are you able to begin training? Have you modified the code?

[hugh920]

@dgbarclay Mine can be trained without modifying the code. However, due to increased memory, it failed in the second round. I modified batch_size and made the model structure a little simpler so that he could continue to run. I noticed that the memory increased during the first two training rounds and stabilized after the third. I don't understand why.

[dgbarclay]

@hugh920 okay, I have not yet made it that far. I was running out of memory during forming the DataLoader so I'm having to refactor a little bit. Are you able to push your version so I can compare the two? It would help me out loads, cheers.

[dgbarclay]

@hugh920 are you able to run eval_nus_wide.sh without failure? I ultimately just need to be able to run this model to take image queries and give predictions, are you able to get the model in that state?

[hugh920]

@dgbarclay I took the ALF out and just used FLF, which didn't work well. It may not be what you need.

[hugh920]

@dgbarclay I also had a problem with processes being killed while loading data on other projects today. I have observed that the GPU is not utilized when loading data. It is a dataloader made by CPU, probably because the processing power of CPU is not up to it.It has nothing to do with memory size or GPU.

[akshitac8]

Is the issue solved?