PHP性能:在Session中存储类对象与静态vs Globals

PHP性能:在Session中存储类对象与静态vs Globals

问题描述:

I've been looking for an answer on this, so far I have been unable to find an answer. My question is; What is the best way to store a huge global class that does not require any dynamic input, it only needs to be used once.

Lets take for example a template class:

<?php
class Design_API{
   function loadfile($file){
     //load file here
   }

   // do file manipulation here

   function presentfile(){
      echo($this->file);
   }

}
?>

Utilizing this class as a basic example of a layout. What would be the best way performance and security wise to use it. Would it be to create an instance of it as a global; store the instance in a session; or simply make it a static class.

Also, say we used a session if 2 clients access the site at the same exact millisecond, would php lock the session file forcing client 2's web load to take longer?

我一直在寻找答案,到目前为止我一直无法找到答案。 我的问题是; 存储一个不需要任何动态输入的庞大全局类的最佳方法是什么,它只需要使用一次。 p>

让我们以模板类为例: p>

 &lt;?php 
class Design_API {
 function loadfile($ file){
 //在此处加载文件
} 
 
 //在此处进行文件操作
 \  n function presentfile(){
 echo($ this-&gt; file); 
} 
 
} 
?&gt; 
  code>  pre> 
 
 

利用这个 class作为布局的基本示例。 使用它的最佳方式是性能和安全性。 是否将它的实例创建为全局; 将实例存储在会话中; 或者简单地使它成为一个静态类。 p>

另外,假设我们使用一个会话,如果2个客户端以相同的毫秒访问该站点,那么php会锁定会话文件,强制客户端2的web加载到 需要更长时间? p> div>

This question is a bit too mixed up to be answered in a consistent way, so here are some points:

  • one client does not block another, unless they're accessing a shared resource
  • sessions are not shared resources between different users, forget about this misconception
  • wherever you store objects hardly makes a difference in performance
  • it makes even less of a difference between different requests and users, since no resources are shared between requests
  • code what you mean first and what is most maintainable, optimize this for performance later when it is proven to be slow (which it likely won't be)
  • avoid globals wherever possible
  • don't store stuff in the session that does not belong there, like code
  • avoid static classes as much as possible, they cause code coupling, which should be reduced
  • static classes are not necessarily faster

The best way to handle this is to make the class a Singleton class and use the static method to instatiante it.

Storing the object in session will involve serialization and de-serialization which is very bad for performance. Also if you store any resources in the class they can't be serialized.