I have turned on Lumen but it is still showing warning to build lighting
I have a Intel Core i5 and 8gb RAM. I have Global illumination and Reflects set to lumen and have restarted the editor. I have also set it in the Post Process Volume. My scalability is set to low for all.
I have turned on Lumen but it still is showing to build lighting.
Is this how lumen works?
Related
We are experiencing very slow processing and converting videos to m3u8 using ffmpeg library.
Note that the operating system used is Ubuntu Server and that the server has huge resources in RAM and CBU, and we noticed that the processing process does not consume the available resources significantly
Average video size: 1 GB
Average video processing time: 2 - 3 hours
The programming language used: asp.net core 3.1
We need to reach a maximum of 20 minutes in processing time, is that possible?
This problem does not seem to be related to programming. It is recommended to take the following steps to test, there should be some test results that can help you.
Use a local computer with a higher configuration of Ubuntu for testing, and it is recommended to install a solid state drive.
If the Ubuntu server you mentioned is a cloud server, it is recommended to upgrade to a higher performance for testing. It is best to test locally before deciding if such an upgrade is needed to save money.
If the above two points are difficult, for example, there is no such Ubuntu, we can also test it on a personal PC with Win 10/11 (with a solid state drive), install the ffmpeg environment, and then ensure that other software resources are closed, only Keep IIS, ffmpeg and other related services for testing.
I personally recommend trying the third suggestion first, so that you can get test results for the problem you care about. If the 1GB video can be processed within 20min, then we can consider upgrading the relevant configuration of Ubuntu.
Is there any possibility of running Orion ContextBroker on Raspberry Pi with Raspbian OS?
The requirements recommended in the Orion documentation are:
Although we haven't done yet a precise profiling on Orion Context
Broker, tests done in our development and testing environment show
that a host with 2 CPU cores and 4 GB RAM is fine to run the
ContextBroker and MongoDB server. In fact, this is a rather
conservative estimation, Orion Context Broker could run fine also in
systems with a lower resources profile. The critical resource here is
RAM memory, as MongoDB performance is related to the amount of
available RAM to map database files into memory.
Besides the board constrained resources, you will have to search about the equivalent required libraries for RaspbianOS.
There is a discussion about it here:
https://github.com/telefonicaid/fiware-orion/issues/15
I'm trying to use the Kinect SDK v1 with an Xbox Kinect sensor. I installed the SDK on my dev machine and I launched the samples. The C# samples do not work, I either get "oops there was an error" or a "NotReady" status and FPS is stuck at -1.
At first I thought this was a problem with the device itself, so I tried installing the SDK on my laptop and the samples work on that fine, both the C# and C++. So the kinect device itself is ok.
I've reinstalled the SDK on my development machine, and I still have the same issues.
Any ideas/solutions?
EDIT: I should note that I have previoulsy developed with this kinect under the 1.0 SDK and when I debug my own app the sensor status enum is still "NotReady"
How is dev machine configuration different from laptop. In the release notes # http://www.microsoft.com/en-us/kinectforwindows/develop/release-notes.aspx it's mentioned that
USB host controller compatibility
The Kinect for Windows drivers have encountered compatibility problems with certain USB host controllers when tested in specific computer configurations. Some examples of these controllers are the AMD Fusion A75 USB2.0 controller, the Etron USB 3.0 Extensible Host Controller, or the Renesas Electronics USB 3.0 Controller. On those controllers, you may encounter a problem, such as a low RGB frame rate, or a Not Ready status when plugging/unplugging a Kinect. These compatibility problems are more likely to occur on PC's running the Windows 8 Developer Preview, or if you plug/unplug multiple devices repeatedly. If this happens to you, you may have to restart your app or reboot your computer. You can also try plugging your device into another USB 2.0 controller.
My application can be fairly CPU-intensive, as can the server I launch from my application using NativeProcess.
The problem is that they're both using the one core. On a quad-core machine, they both slow to a crawl as they're severely limited on their CPU share.
Is there any way to launch a native process on a different core, or in a way that won't result in such a shared, throttled bottleneck?
If you already using NativeProcess, you could also set CPU affinity in platform specific way.
My Grails application is running in a development environment. I still didn't go into production, but in any case, is it normal that my Grails application is requiring 230 MB at startup only (with an empty bootstrap and no request handled so far)?
Do you know why this is the case, how to improve memory usage in development mode and, most important, whether it is reduced in production environment?
To answer your questions, yes - it is normal. It's especially normal if you have a lot GSPs in your application. GSPs are runtime compiled so you can speed up their generation by increasing your permgen space.
You can improve memory use and performance in general by making sure that you are passing the '-server' flag when you load your server JVM.
I wouldn't blame all that memory usage just on Grails. Because it uses an embedded Tomcat (Jetty in older versions) there will be a decent amount of overhead even when running an empty application.
IMO, 230MB is a lot of memory use for a Java application. High memory usage is just part of life when writing jvm based applications.
My online Grails applications run in a VPS with only 512MB (which includes a Drupal CMS, Apache, the email services, ... and the Tomcat to run GRails) so you can definitely tune your application to use less memory