10:56 am
July 27, 2023
The memory usage of the plugin is directly tied to the size of the content it processes. However, predicting the exact memory usage is challenging due to the variability in content. The plugin itself consumes less than 500 kilobytes of memory (approximately 3 times less than an 80s standard 3-1/2 inch floppy disk), which is just nothing in terms of today's standards.
Most of the memory consumption is driven by your feed content: the XML files of the feeds, the HTML articles extracted from these feeds, and even image files when they're loaded to your server and processed for tasks like cropping featured images. Essentially, you have full control over how much memory the plugin uses as you manage the content it processes. As the plugin's developer, I have no control over this process.
If you encounter a memory overflow issue when clicking the "Pull selected feeds now" button or during scheduled syndication, it's likely due to the size and complexity of the content being processed. You might consider optimizing your feeds or server resources to manage memory more effectively.
3:04 pm
July 27, 2023
CyberSEO said
The memory usage of the plugin is directly tied to the size of the content it processes. However, predicting the exact memory usage is challenging due to the variability in content. The plugin itself consumes less than 500 kilobytes of memory (approximately 3 times less than an 80s standard 3-1/2 inch floppy disk), which is just nothing in terms of today's standards.Most of the memory consumption is driven by your feed content: the XML files of the feeds, the HTML articles extracted from these feeds, and even image files when they're loaded to your server and processed for tasks like cropping featured images. Essentially, you have full control over how much memory the plugin uses as you manage the content it processes. As the plugin's developer, I have no control over this process.
If you encounter a memory overflow issue when clicking the "Pull selected feeds now" button or during scheduled syndication, it's likely due to the size and complexity of the content being processed. You might consider optimizing your feeds or server resources to manage memory more effectively.
I'm talking about RAM, not disk space.
I answered you about RAM only. The plugin doesn't use any disk space for its work. It runs in the server's memory and there it processes all the content sources including images. To generate a post thumbnail, your server has to download the image into its memory and process it there, similar to what applications like Photoshop do on your desktop PC.
Check this out, because I believe it answers to your question: Login to see this link
The same is true for the textual data. So when the plugin processes an RSS feed, it creates a PHP XML DOM object in memory and works with it. If your feed has, say, 100 entries, it will generate quite a large data structure in the server's RAM.
So the memory usage depends entirely on the size of the data you process with the plugin. The plugin cannot overflow your server's memory, but your content can.
Most Users Ever Online: 541
Currently Online:
16 Guest(s)
Currently Browsing this Page:
1 Guest(s)
Top Posters:
ninja321: 84
s.baryshev.aoasp: 68
Freedom: 61
Pandermos: 54
MediFormatica: 49
B8europe: 48
Member Stats:
Guest Posters: 337
Members: 2816
Moderators: 0
Admins: 1
Forum Stats:
Groups: 1
Forums: 5
Topics: 1625
Posts: 8271
Newest Members:
jeremyboucher, lthompson2709, MAC, duty3canada, backlinkmorocco, dmitrypehovskiworkAdministrators: CyberSEO: 3909